Considerations for Allowing Duplicate Data.com Records in Salesforce | Salesforce
Organizations that use a sharing model may want to allow Data.com users to add duplicate account, contact, or lead records to Salesforce.
|Available in: Salesforce Classic and Lightning Experience|
|Available with a Data.com Prospector license in: Contact Manager (no Lead object), Group, Professional, Enterprise, Performance, and Unlimited Editions|
Keep these considerations in mind when setting your duplicate preferences.
- Records are considered duplicates when they have the same Data.com ID number in the Data.com Key field. This includes records that were added from Data.com as both contacts and leads.
- You can allow duplicates by object for the entire organization—not for individual users. If, however, you want to prevent a user or profile from being able to add duplicates, you can create a trigger.
- Records that are already in Salesforce are marked with a green dot () in search results. These records can be re-added by any Data.com user if your organization allows duplicates for the object.
- Records that have been added to Salesforce from Data.com are marked with a blue checkmark () in search results. These records can be re-added by any Data.com user if your organization allows duplicates for the object. Adding a record affects the record balance only the first time that record is added to Salesforce: adding duplicates does not affect the record balance.
- If your Data.com preferences are set to allow duplicates but your organization also uses duplicate rules to prevent the creation of duplicate records, the duplicate rule will determine if the duplicate record is allowed or blocked.