Avoid duplicates of existing Destination SMTP addresses (Dynamic Exclusions)2017-05-18 17:34:49
Exclusions Features Troubleshooting UnitySync
One of the most common questions we’re asked is, “How do I keep duplicate SMTP addresses out of my Destination Directory?”
We used to recommend a method called Dynamic Exclusions which may be familiar to some of you. Now, however, UnitySync can perform your Sync and avoid duplicates without the need for a separate Dynamic Exclude connection.
UnitySync by design does not actively read the Destination directory to detect duplicates, however you can configure your connection to Create and Join (Both) to prevent duplicate mail addresses or objects.
When a you set your Sync/Join Mode to Both, you are utilizing both Create and Join functionality. When a Both connection runs, it will search for an existing Destination object based on your Join criteria. If an existing object is found, it will be linked and updated, if applicable. If no existing object is found, a new object will be created based on the Create criteria. If a Source object is deleted (or falls outside the scope of the sync) the corresponding Destination object may be deleted, depending on your Delete Processing settings.
Recommended process to set up Create/Join properly to avoid duplicate SMTP addresses:
- On the Destination tab under Sync/Join Mode, select Both.
- Under Join with existing objects, add a query in each field necessary.
- Check your Source tab to verify what types of objects you have elected to sync
- Add this recommended query string for each matching query field on the Destination tab (i.e., if you’ve selected to sync Users and Contacts on the Source tab, you’ll need to populate the User(s) query and Contact(s) query) on the Destination tab:
- Also under Join with Existing Objects, select Reject on Match.
Reject on Match applies to the Join portion of the sync. When Reject on Match is enabled, Join functionality is configured so that only Destination objects found within the configured Sync Container may be touched. If an object is found outside the Sync Container, the object is ignored, and a Join Match warning is logged.