Delpha’s Master Record Rule helps you define which duplicate to keep during merges. Choose from built-in rules -oldest, latest, or most-filled...- to ensure accurate and complete Salesforce data.
To define which record survives during a merge, Delpha uses Master Record Selection Rules.
Open the Delpha Setup App and go to the Duplicate Settings tab.
By default, Delpha selects the oldest record as the master and fills any empty fields with values from the duplicate. This ensures completeness and consistency in the final, merged record.
These rules help you tailor your merge logic to preserve the most reliable or relevant data.
Rule
Description
Oldest created date
Selects the record with the earliest creation date
Latest created date
Selects the most recently created record
Oldest modified date
Selects the record with the earliest last update
Latest modified date
Selects the record with the most recent update
Most Filled
Selects the record that has the most populated fields
Configure Delpha’s master record selection rules and predefined values to automate duplicate merges. Ensure clean, consistent data with flexible merge object logic.
The Merge Object Rules Section lets you define how the master record is selected and how field values are handled when merging duplicates:
Master Record Selection – Set the default rule for picking the surviving record (e.g., most recently updated, highest score).
Custom Rule for Master Record Selection – using advanced conditions.
Default rules for field selection – , ensuring compliance with business rules.
These rules help automate and standardize merge behavior across all duplicate resolution workflows.
Delpha merge field rules ensure high-quality Salesforce data by selecting values based on creation/modification date or data completeness. Choose the best default rule for your duplicate resolution.
Once the master record is selected during a merge, Delpha needs to determine how to choose the final field values. By default, it uses the Master and Not Empty rule.
These rules help ensure Delpha always retains the most complete and relevant data in the merged
Uses field from earliest update, but skips if value is empty
Latest modified date & not empty
Uses field from latest update, but skips if value is empty
Rule
Description
Oldest created date
Uses the field from the earliest created record
Latest created date
Uses the field from the most recently created record
Oldest modified date
Uses the field from the earliest updated record
Latest modified date
Uses the field from the most recently updated record
Oldest created date & not empty
Uses field from oldest record, but skips if value is empty
Latest created date & not empty
Uses field from latest record, but skips if value is empty
Oldest modified date & not empty
Customize duplicate merges with Delpha’s Custom Master Record Rule. Use formula-based scoring to prioritize records and define fall back to creation date for tie-breaking.
If your merge logic needs to follow more advanced or business-specific rules, Delpha allows you to define a Custom Master Record Rule. This approach lets you assign a score to each record in a duplicate pair based on a custom formula and select the one with the highest score as the master.
Define a Custom Scoring Field
Create a formula field (e.g., DC_MasterScoring__c) to assign points based on your business rules.
Example Use Case:
If Account Type = Customer → +10 points
This setup allows your master record selection process to reflect your business priorities precisely.
If Account Type = Target → +1 point
Otherwise → 0 points
Set the Custom Rule Expression
Use:
DC_MasterScoring__c Desc, CreatedDate
This tells Delpha to:
First, select the record with the highest custom score
Then use the oldest created date as a fallback if scores are equal
Use Case Logic Covered:
Customer > Prospect > Target > Oldest