Free Edition Data Stewardship

OneMerge Free Edition Summer '24

OneMerge Free Edition provides data stewardship tools in the Summer 24 release. This blog post provides an overview of the new features.

I’ll start this post with a bullet-point summary of the key concepts of the OneMerge data flow.

  • Duplicate Rules identify duplicate records one at a time using a matching algorithm defined by a Matching Rule (both rule types are standard Salesforce features).
  • Duplicate Rules configured with the Report option report duplicates as Duplicate Record Items within a parent Duplicate Record Set (both standard objects).
  • Duplicate Record Sets support reporting and manual compare-and-merge use cases.
  • OneMerge extends the standard use cases with automated, rules-based merge.
  • Merge Jobs are scheduled for a Salesforce Object to merge Duplicate Record Sets generated by Duplicate Rules for the same object.
  • Merge Jobs apply the merge configuration for the Salesforce object.
  • Merge Rulesets define the merge behaviour for a Salesforce object i.e. priority logic for selecting the surviving record.
  • Merge Rules group fields which should be merged together (e.g. email+channel consent) and add priority logic for selecting the surviving values.

By default the merge is fully automated; when a scheduled Merge Job executes for a Salesforce object, all Duplicate Record Sets for the same object are merged. In most cases this is the desired behaviour, the reported duplicates have been identified by Matching Rules which can be validated and refined to deliver an accurate and valid outcome and as such duplicate merge should not normally require manual intervention. There are however scenarios where a manual review step is necessary before the automated merge; examples being where the matching algorithm is relaxed to capture more potential duplicates or where the type of data or compliance environment requires the explicit approval (to merge) by a data steward. With the Summer ’24 release of OneMerge Free Edition it is now possible to limit the Duplicate Record Sets that are merged to those which have been approved. The sections below show the new features which support the implementation of a data stewardship process for your Salesforce CRM data.

Duplicate Record Set – Merge Decision Field

This field can be set to Accepted or Rejected values manually by a Data Steward who has reviewed the duplicate records, or the field value could be set by a record triggered Flow which could evaluate the records and make an automated decision to accept, reject or defer to manual review.

Duplicate Record Set Merge Decision

Duplicate Record Item – Is Preferred Master? Field

This field enables the Data Steward to override the automated priority logic for selecting the surviving record.

Duplicate Record Item Is Preferred Master?

Application Setting – Is Data Stewarding?

This setting activates data stewarding; once ticked Merge Jobs are limited to processing Duplicate Record Sets with the field Merge Decision set to Accepted.

Application Settings - Is Data Stewarding?

Data Stewardship Flow

This template flow can be used as-is to review Duplicate Record Sets and set the Merge Decision and Is Preferred Master? fields. The flow can also serve as the template for new flows with specialised behaviour.

Data Stewarding Flow - Select Object and Duplicate Rule

Data Stewarding Flow - Select Duplicate Record Set

Data Stewarding Flow - Set Merge Decision and Preferred Master

Data Stewarding Flow - Outcome Confirmation

Please note, the commercial editions of OneMerge include more sophisticated and flexible data stewardship features including data stewardship conditions and real-time merge following acceptance.

Thanks for reading.

Filed under