Enabling Duplicate Checking Among Person Accounts, Leads, and Contacts
The duplicate contact check batch job does not identify duplicates between person accounts and contacts or leads by default. To match person accounts against contacts or leads, convert the contacts or leads to person accounts., and then run the duplicate check batch job. To match person accounts against contacts or leads without converting them to person accounts, enable the lead person account comparison setting.
To enable duplicate checking among person accounts, leads, and contacts, you can set enableLeadPersonAccountComparison to true. By default, enableLeadPersonAccountComparison is false. Ensure you are aware of the impact to Informatica Cloud Customer 360 (
) batch processes when you enable duplicate checking among person accounts, leads, and contacts.
The following code sample enables duplicate checking among person accounts and leads and contacts:
The following batch jobs are affected when you enable duplicate checking among person accounts, leads, and contacts:
Duplicate Contact Check
Checks for duplicates among person account contacts, leads, and business account contacts. You can see the duplicate pairs identified by this batch job in the Other Duplicates tab.
Checks for duplicates among person accounts. You can see the duplicate pairs identified by this batch job in the Duplicates tab.
Merges the person account duplicate pairs identified by the duplicate check, but does not merge duplicate pairs identified by the duplicate contact check.
Merges pairs of the same object types. For example, business account contacts are merged with business accounts contacts. Pairs that are of different object types are not merged. For example, person account contacts are not merged with business account contacts.
Merges pairs of leads. Leads are not merged with objects that are not leads.