Merge Field Rules section
Use Delpha’s Merge Field Rules to control which values are kept during Salesforce merges. Apply control specific automated logic,different from the default one.
Merge Field Rules – Field-Level Control for Smarter Merges
The Merge Field Rules screen lets you override the default behavior set in the Merge Object Rules. This powerful interface allows you to define exactly which value should be kept for each field during a merge—ensuring consistent, automated decisions that align with your data governance policies.
Rule Name
The label for your merge rule (can be customized).
Action
Indicates whether the field is grouped or individually customized.
Field
The API name or label of the field the rule applies to.
Override Rule
Specifies what value to keep: e.g., Master and Not Empty, Highest Value, or Empty.
Operation
Special logic applied (e.g., ConcatenateUnicity to merge unique values).
Visible
Whether this field is shown in the bot deduplication conversation.
Active
Whether the rule is currently being used during merge operations.
How It Works
Each row in the panel defines a rule for a specific field, guiding how the final merged value is selected.
Common Rule Types:
Master and Not Empty: Keep the master record’s value—unless it’s empty.
Highest Value: Ideal for dates or numeric fields (e.g., latest activity).
Empty: Clears the field value post-merge.
ConcatenateUnicity: Combines unique values (perfect for multi-entry fields like tags or IDs).
Impact on Merge Operations
These rules are applied when you Accept a merge from the Duplicate Steward View. As a result:
The best value is selected automatically
Manual review is minimized
Merges stay clean, reliable, and aligned with business rules
➕ Adding a New Rule
Click New (top right) to define a custom merge behavior for any additional field.
Last updated
Was this helpful?