We would like the ability to set the Email Type and Primary Email flag in Altru only if a new constituent is being added to Altru in an OIC formula. As it stands now, we have those fields unmapped because we don't want to risk OIC changing a record's existing Email Type or Primary Email Address. This means we have to go into any new records created by the formula and manually set the Email Type and Primary Email flag.
Is this need limited to Email-related fields or do you have any other examples of fields that you would only populate on new records? For example, a specific constituent code or solicit code?
Most relevant to us would be Address fields. In MC > AL formulas we'd like to be able to add an Address that is just a ZIP code to new records, but not to existing Altru records.
Not relevant to us but possibly relevant to other orgs would be constituent code and solicit code, as you mentioned. Of course, the formula can already be set to prevent duplicate constituent or solicit codes from being added to existing records, so limiting the appending of the code itself may not be as important as making sure the Date From or Start Date doesn't get overwritten on the Altru side if the constituent/solicit code already exists there. (See my "Map attribute data only for new records" idea.)