Within the integration between Salesforce and Azavista, duplicate handling follows the system-defined identifier hierarchy. Users cannot configure which fields act as unique identifiers.
When Salesforce Record ID Is Used
- The Salesforce Record ID is the authoritative identifier.
- Matching is strictly ID-based.
- Updates occur on the correct record.
- Duplicate creation does not occur through ID-based sync.
When Email Is Used as Fallback (Contacts Only)
- Email is only used if no Salesforce Record ID exists (initial sync or record creation).
- Multiple Contacts with the same email can cause:
- Sync errors
- Ambiguous updates
- Creation of additional duplicates
- Once a Salesforce ID is stored, email is no longer used for matching.
- Email-based matching assumes email values are unique and properly maintained.
Clarification on “External ID”
- “External ID” in this integration refers to the Salesforce Record ID stored in Azavista.
- It is not a configurable custom field.
- Users cannot select or replace identifiers.
Why Duplicates Occur
- Multiple Contacts with the same email in Salesforce.
- Pre-existing duplicates before synchronization.
- Parallel record creation in both systems before Salesforce ID is established.
The integration does not merge duplicates automatically.
Best Practices to Prevent Duplicates
- Ensure Email uniqueness for Contacts in Salesforce
- Clean existing duplicates before enabling sync
- Avoid manually creating records in both systems
- Maintain Salesforce Record IDs as the primary sync anchor