Merge Settings

After configuring a duplicate matching rule and condition, navigate to the Merge Settings tab. Here, you can define one-to-many and many-to-many record relationships for merging related records, as well as establish criteria for selecting a master record.

Fill in the below fields:

• One to Many Relationships: In this field, you can select the One-to-Many record relationships based on which all the selected related records will merge into master record from the subordinate records.

• Many to Many Relationships: In this field, you can select the Many-to-Many record relationships based on which all the selected related records will merge into master record from the subordinate records.

• Master Deciding Rule: Establish the selection criteria for the master record to which duplicate records will be merged. You may choose from one of the following criteria:

  • Latest Modified: If you set the ‘Master Deciding Rule’ as ‘Latest Modified’, then duplicate/subordinate records will be merged with latest modified record.

  • Oldest Modified: If you set the ‘Master Deciding Rule’ as ‘Oldest Modified’, then duplicate/subordinate records will be merged with oldest modified record.

  • Latest Created: If you set the ‘Master Deciding Rule’ as ‘Latest Created’, then duplicate/subordinate records will be merged with latest created record.

  • Oldest Created: If you set the ‘Master Deciding Rule’ as ‘Oldest Created’, then duplicate/subordinate records will be merged with the oldest created record.

  • Most Field Values: If you set the ‘Master Deciding Rule’ as ‘Most Field Values’, then duplicate/subordinate records will be merged into the record with most field values filled.

  • Most Activities: If you set the ‘Master Deciding Rule’ as ‘Most Activities’, then duplicate/subordinate records will be merged to record with the most activities.

• Criteria Based: You can also set ‘Master Deciding Rule’ based on filter criteria or conditions (conditions defined in Fetch XML). For example, if you want to set ‘Master Deciding Rule’ as ‘Active Contact’ that contains a specific ‘Company Name’, then you can do so by entering a Fetch XML code for the same.

Note: If multiple records meet the same Master Deciding Rule criteria (e.g., all duplicate records have the highest number of activities when ‘Most Activities’ is selected), the system automatically sets the latest modified record as the master.

• Bypass Background Processes: Enable this feature to enhance data operation speed by bypassing all background processes like plugins, workflows, actions, and Power Automate flows while merging duplicates.

This option is available under the “Merge Setting” tab of the Entity Configuration window.

Steps to Configure:

1. Navigate to Entity Configuration within DeDupeD.

2. Open the entity for which you want to modify merge behavior.

3. Go to the Merge Settings tab.

4. Locate the Bypass Background Processes section.

5. Select one or more of the following options as per your requirement:

6. Synchronous Plugins, Workflows, Actions

7. Asynchronous Plugins, Workflows, Actions

8. Power Automate Flows

9. Click Save & Close to apply the configuration.

Option	Description
Synchronous Plugins, Workflows, Actions	Bypasses synchronous processes to allow immediate merging without delays. Useful for improving speed during large merge operations.
Asynchronous Plugins, Workflows, Actions	Bypasses asynchronous background operations that may otherwise trigger post-merge actions. This helps prevent performance bottlenecks.
Power Automate Flows	Skips the execution of Power Automate flows during the merge process, ensuring the merge runs uninterrupted and avoids triggering unnecessary automations.

Example Scenario

When performing bulk merges on thousands of duplicate records, enabling the Bypass Background Processes options helps reduce execution time and system strain. For instance, if Power Automate flows are not required during the merge, you can bypass them to avoid unnecessary flow runs, ensuring faster and more efficient merging.

• Ignore Fields from Merge

The Ignore Fields from Merge feature in DeDupeD gives users greater control over which data fields are merged during duplicate record consolidation. Located under the Merge Settings tab of the Entity Configuration, this feature allows users to exclude specific fields from the merge process to preserve existing data or prevent unwanted overwrites.

When a field is added to this list, its value will remain unchanged and will not be merged into the master record during the merge operation.

Steps to Configure:

1. Navigate to Entity Configuration in DeDupeD.

2. Open the desired entity configuration record.

3. Go to the Merge Settings tab.

4. Locate the field Ignore Fields from Merge from section Select fields to exclude from merge..

5. Click inside the dropdown list to view all available fields for that entity.

6. Select one or more fields you want to exclude from the merge.

7. Click Save & Close to apply your configuration.

Example

If you select the field Address1_City under Ignore Fields from Merge, then during the merge:

• The City field value will not be merged or overwritten from any duplicate records.

• The master record will retain its original City value, even after the merge.

Image 1: Configuration interface showing the option to exclude fields from merge.

Image 2: Example where Address1_City is selected, ensuring the field is ignored during merging.

To enable these merge options in CRM, you need to do the following configurations:

1. Auto Merge

2. Field Merge

3. Address Merge

For further queries, reach out to us at [email protected]