Cross-Entity Merge Settings

Entity Configuration

Cross-Entity Merge Settings

With Duplicate Manager, you can merge records across different entities.

Before using this functionality, configure the merge behavior for the involved entities.

Changing the Cross-Entity Merge Settings


  1. Open the Duplicate Manager App and navigate to Entity Configuration.
  2. In the top panel, click the currently selected entity’s name to open the Entity Select Dropdown, and choose the entity you want to configure.
  3. In the top panel, beneath the entity name, select the tab Cross-Entity-Merge.
  4. Adjust the settings as described below, then click Save to apply your changes.

 

Column Mappings


When merging records from two different entities, you first need to define column mappings between them.
Since different entities often don’t share identical columns (names, data types, or formats), Duplicate Manager needs to know which columns from one entity correspond to which columns in the other.

Column mappings define where data from one entity will be transferred during the merge process.
For example, the entity Lead might have a column called “Account Name”, which represents the same type of information as the “Name” column in the Account entity.
By creating a column mapping between Lead.Account Name and Account.Name, you ensure that the correct data is merged between both entities.

Only mapped columns will be selectable when merging records of different entitites. Unmapped columns will be ignored and retain their original data.

You can check each mapping using the icon on the left. If a mapping could potentially cause issues during merging—for example, if the string lengths of the mapped columns differ—the icon will display an exclamation mark. Hover over the icon to see detailed information about the issue and take the necessary steps to correct the format before proceeding.

Restrictions for mapping


The following rules show restrictions of what kinds of data can be mapped:

  • Both columns must be of the same type and the same format.
  • The target column can’t be mapped to another column already.
  • Lookup Columns must reference the same entity.

Furthermore, columns with the following properties are not mappable:

  • Columns that are not addable to a form (AttributeMetadata.IsValidForForm).
  • Columns that are readonly (AttributeMetadata.isValidForUpdate).
  • Columns of the follwing type:
    • Virtual
    • PartyList
    • Picklist
    • State
    • Status

Next Steps


Configure Rules, change the Duplicate Prevention or set the Entity Settings.

dm_icon_512x512

Didn't find what you were looking for?

Our team is ready to support you - reach out anytime and we’ll make sure you get the help you need.