A number of use cases have come up from clients where they want to make decisions based on whether or not the imported record has matched to a Constituent. For example, only import records that are updates and do not import net new records, or to default an related organization to a generic record where a match has not been made. This is currently not possible because all GUID fields are hidden from orchestrations when selecting fields.

To address any concerns that these fields should only be written to by BVDL, ensuring referential integrity, one option would be to make select GUID fields available only on the LEFT hand side of the orchestrations. This way we could create out of the box orchestrations that would check for a value in Constituent.CRMID, the field that stores the CRM Constituent Record ID (GUID), but we would not be able to select that field to write to. This would open up a lot of possibilities for users who otherwise need a SQL orchestration or to import/export/re-import data to meet their business needs.