Merge Rules

Last published at: 2022-02-11 15:32:56 UTC
Delete

This article discusses the old merge rules feature. Information about the new Advanced Merge Rules is available in this knowledge item.

Delete

The 'Basic Merge Rule' is available in our Advanced plan. The 'Extensive Merge Rules' (per field) are available in our Premium edition.

When merging records within an Object, Duplicate Check uses a certain strategy on what value and field to keep. The Merge Rules setting lets you define the 'merge rules' when using the Merge and Auto Merge features.

In the standard configuration the 'general merge rule' is 'last modified'. This means that if two or more records are merged by the Auto Merge feature, the record that is last modified will be kept in the merging process.

Delete

Learn more about Auto Merge.

Duplicate Check will always take a field with a value over a field with no value, no matter the rule.

The Master Record Rule and the options for setting a merge rule: Last Modified, Oldest Modified, Last Created, Oldest Created are available in Advanced and Premium Versions. The Field Merge Rules and additional options for setting a merge rule: Field Based and Value Based are available in our Premium version only. 

Modification Based:

General Rule Last Modified Duplicate Check will pick the Last Modified record as a Master record.

Oldest Modified

Duplicate Check will take the Oldest Modified record as a Master record.

Creation Based:

General Rule Last Created Duplicate Check will pick the Last Created record as a Master record.

Oldest Created Duplicate Check will pick the Oldest Created record as a Master record. 

Field Based:

General Rule  Field Based
 Field   Choose a field
Field Rule  Choose a rule
Fallback Rule When defining a specific strategy per field, there is a possibility of both fields to be equal. The fallback rule will decide which fields will be kept. 

Value Based:

General Rule Value Based
Field Choose a field
Field Value Choose a value
Fallback Rule When defining a specific strategy for a value, there is a possibility both values to be equal. The fallback rule will decide which field value will be kept. 

General 'Fallback Rule'

When defining a specific strategy per field, some strategies need a fallback rule. For example, when using 'highest value' for 'annual revenue', there is a possibility both values are equal. The fallback rule will now decide which field will be kept in the last modified record.