Hi XM Community,

My org is using ExternalReference as our sole identity resolution rule and we want to see if we can avoid triggering a contact creation when a record (whether in a workload, file upload, etc.) contains an ExternalReference value which does not already exist?

i.e. if I upload a contact with ExternalReference 1234, and there is no match for it in the system, I want to discard the record, not add the contact. If I upload contact w/ Ext. Ref. 123 and it is found, I want to update that existing contact.

We have a team that populates the directory via API, so we prefer to allow them to manage the contacts and want to minimize erroneous info and unverified contacts added from secondary systems. We utilize workloads, manual file uploads, and the Qualtrics File System to quickly populate lists (sometimes thousands of contacts, so hand choosing contacts is out of the question), so we’re looking for directory level settings or logic to satisfy this requirement.

Anyone resolved a similar requirement?