This is an old revision of the document!
NOTE: Please see Custom Settings for information on how to activate the relevant entities for de-duplication.
Before selecting the related entities dedupe, please go to Custom Settings to configure the related entities you would like to display on this screen. Loading all related entities will reduce performance. Please only select the Account/Contact/Lead related entities utlised in the Post Merge Dedupe process.
Select Entity: Select the one of the following entity to apply the settings for:
Related Entities: All the entities displayed to you which are having 1:N relationship with the base entity selected.
Add Post Merge Settings: To add the settings for the related entity, you will need to drag-and-drop the related entity from the left hand side onto the ‘Post Merge Configuration’ grid on the right hand side.
You have 3 actions to choose from:
Attributes configuration for Duplicate Detection: Select the attributes (by dragging and dropping from the left to the right hand side) for duplicate records detection. If the selected attributes values are found to be the same, then the records shall be declared as duplicates.
Additional Settings: You can apply the following additional settings to pre-process the data before duplicate detection:
Primary Record Detection Attribute: Select the attribute from the list which will help to detect the Primary Record. You can select the ‘None’ option if you don’t want to apply ‘Primary Record Detection Settings’.
Primary Record Defining Attribute: This is an optional feature. You can select the attribute (of type ‘Option Set’) from this list if you want Primary Records per option. E.g. If you select the ‘Communication Type’ attribute for the related entity ‘Phone’, you will receive the primary record for each communication type against the Master record.
Best Primary Record Detection Rules: You can set the rules in sequential manner for detection of primary record(s).
There are two ways to select an 'Edit Existing Setting':