OneMerge Free Edition Summer 24

Release Overview

This post provides an overview of the OneMerge Free Edition Summer 24 release.

1. Default Merge Rule Priority

Just a quick recap before I introduce this enhancement. Merge Rules group fields that should be merged together from one record within a set of identified duplicate records. The best example of a grouping of fields is an address; in most cases it doesn’t make sense to take the City from one record and the Street from another, instead all fields i.e. the complete address, are taken from just one record. The selection of which record this is (amongst the set of duplicates) is determined by the priority type set for the Merge Rule. This could be recency priority i.e. the newest or oldest, or quality based priority. For recency priority, we need to specify which date or datetime field to reference to order the duplicate records (ascending or descending) before taking the values from the top record in the ordered list. It’s possible to use the record-level Created Date or Last Modified Date standard fields as the reference or a custom field. OneMerge provides custom fields for standard field groupings; for example the Mailing Address Last Updated field tracks when any Contact Mailing Address field last changed so the ordering can be specific to the fields involved and not affected by unrelated record modifications. Similarly, for quality priority we need to specify which numeric field to reference to order the duplicate records (descending; highest value wins) before taking the values from the top record in the ordered list. It is typical to use a Salesforce Formula Field to calculate the required quality metric; for example an Address Quality Score based on completeness.

Prior to the Summer ’24 release, the fields referenced for Merge Rule Priority could be set at the Merge Rule level (Newest or Oldest based on Create or Last Modified Date) or as a Merge Rule Field (flagged as Is Priority? or Is Secondary Priority?).

With the Summer ’24 release it is now possible to set a default Merge Rule Priority at the Merge Ruleset level and then set the priority type for each Merge Rule to Default. This simplifies the configuration of Merge Rules which share a common prioritisation. For example, a Merge Ruleset could select the Master Record based on the oldest Created Date and then select Merge Rule field values based on the newest Created Date.

2. Rollback now undeletes losing records

The Merge Rollback feature has been extended in the Summer ’24 release to enable recovery of losing records that have been deleted and moved to the Salesforce Recycle Bin. Note, availability of deleted records in the Salesforce Recycle Bin is subject to time and usage factors; please consult the Salesforce Help for additional information.

The Summer ’24 release also adds a new Is Check Only? option which allows the outcome of the rollback process to be viewed without making permanent data changes.

OneMerge Rollback Action

Merge Rollback now supports undelete for losing records

3. Updated Home Page

The OneMerge App Home Page has been redesigned for the Summer ’24 release with a restructured dashboard and a new Guidance tab.

OneMerge Home Page

Updated Home Page Dashboard Design

The dashboard analytical components are now placed in context under headings which describe the end-to-end duplicate management process.

The new Guidance tab provides convenient access to the Setup Steps and also the infographic diagram which provides an outline of the end-to-end duplicate management process.

The release notes for the Summer ’24 release can be found at

Thanks for reading!

Filed under