Use Case: RE-Nxt to Salesforce (for Email)

We are integrating RE Constituents to Salesforce to utilize Account Engagement to send our emails. As such, we are only sending down a few fields { Cons-ID, First, Middle, Last, Email..}. The formula is based upon Constituent-Date-Changed in RE. There's lots of things on a Constituent record that get "touched" each day that triggers a change to the Constituent-Date-Changed field, despite there be no effective change to the fields in our formula.

Even after getting a Primary Match across Constituent-ID, we would like to implement a Custom Routing to Omit if *all of the Source Field values are the same as the Destination Fields across {First, Middle, Last, Email Address, etc.}.

Currently we cannot do this as Customer Routing-Omit only allows comparing Source Fields to literal values.

We feel that we could Omit maybe 80% of the Ready Records and not burn the carbon of a POST to Salesforce that essentially wouldn't change any field values.

We realize that this technique may not apply to formulas that have many, many more fields mapped beyond the set of those used in matching, but it would help us or anyone in a similar situation where an intelligent Omit could save time and unnecessary processing.