Getting Started

OneMerge is available via our Salesforce AppExchange listing in 2 ways;

(1) Preconfigured Trial Org.

A preconfigured trial which includes the test records referenced in the exemplar test scenarios covered in the Getting Started with the One Merge Trial video.

(2) Installation into your Org (Sandbox only for trial purposes).

Alternatively, our Release Notes page provides the package version installation link for the latest release.

Once the app is installed please review the Post Installation instructions.

Further help and Training Articles can be found here.

OneMerge extends the standard Salesforce features for duplicate record identification with automated Merge Rules. The standard Salesforce Duplicate Management features noted below require configuration.

Matching Rules compare records and detect duplicates. Standard preconfigured Matching Rules are provided for the standard Salesforce Objects (Account, Person Account, Contact and Lead). Custom Matching Rules can also be configured for standard and custom objects. Matching Rules combine fields with matching logic to define the criteria upon which duplicate records are identified.

Duplicate Rules specify the handling process applied to the duplicate records identified by Matching Rules. Duplicate Rules can Block the creation of duplicates, Alert the user or Report the duplication to a standard object for reporting purposes. OneMerge uses the records generated by the Report action (Duplicate Record Sets) as the input to the automated merge process.

Further help and Training Articles can be found here.

Merge Rulesets define the merge configuration for the specified Salesforce Object. The Merge Ruleset configuration can be managed via the Guided Setup link shown in the page footer of the OneMerge app, this our recommended approach. Alternatively, the configuration can also be managed in the Custom Metadata Type of the same name which is accessible via the Salesforce setup menu or the Merge Ruleset Status panel displayed on the Home tab of the OneMerge app.

OneMerge installs default Merge Rulesets for the Account, Contact and Lead objects and also for Person Accounts if this feature is enabled. The default Merge Rulesets can be modified to meet your merge requirements in the following ways.

• The Master Record Priority can be modified to change the logic applied when determining which record should be the winning record across the identified duplicates. Typically this would be the oldest record by created date or an existing master.
• The Merge Action can be changed from Platform Merge (which uses the Salesforce merge function) to Custom Merge which allows the losing records to be retained.
• Merge Platform Events published by OneMerge can be enabled for notification purposes.

Further help and Training Articles can be found here.

Merge Rules define the logic applied in the intelligent population of the winning record fields (e.g. the most recent communication preferences, the highest quality billing address).

The Merge Rule configuration can be managed via the Guided Setup link shown in the page footer of the OneMerge app, this our recommended approach. Alternatively, the configuration can also be managed in the Custom Metadata Type of the same name which is accessible via the Salesforce setup menu or the Merge Ruleset Status panel displayed on the Home tab of the OneMerge app.

OneMerge installs default Merge Rules for standard fields on the Account, Contact and Lead objects and also for Person Accounts if this feature is enabled.

The default Merge Rules can be modified to meet your merge requirements in the following ways.

• New Merge Rules can be added for Standard Fields which are not covered or for Custom Fields.
• Additional fields can be added to the default Merge Rules.
• The Merge Rule priority can be modified to change the logic applied when populating the winning record from the identified duplicates.

Further help and Training Articles can be found here.

Data Stewarding Conditions pause the automated merge of identified duplicate records where records meet specified criteria. For example a fashion retailer may wish to data steward record merges involving VIP customers or where the lifetime value is above a given threshold; other merges should be fully automated.

Data Stewarding Conditions can be managed via the Guided Setup link shown in the page footer of the OneMerge app, this our recommended approach. Alternatively, the conditions can also be managed in the Custom Metadata Type of the same name which is accessible via the Salesforce setup menu or the Merge Ruleset Status panel displayed on the Home tab of the OneMerge app.

Data Stewarding can be configured to meet your requirements in the following ways.

• Data Stewarding Conditions can be added to a Merge Ruleset and will be evaluated at the pre merge stage to determine whether data stewarding is required.
• Data Stewards can be given convenient access to Data Stewarding Tasks using standard Salesforce features (List views and Reports). Note, the data stewarding task in context is simply to provide a Merge Decision (Accept or Reject) for the referenced Duplicate Record Set.
• Data Stewards can be proactively notified of pending Data Stewarding Tasks using standard Salesforce automation features (Flow) or reporting notifications.
• If all duplicates should be Data Stewarded ensure the App Setting “Is Data Stewarding?” is set to TRUE. OneMerge App Settings are found on the Custom Settings page in the Salesforce setup menu.

Further help and Training Articles can be found here.

Having configured Salesforce Duplicate Management and OneMerge Merge Rules the final step is to activate OneMerge for Realtime merge or to schedule the Merge Job to process merge actions in bulk periodically.

Note, OneMerge App Settings are found on the Custom Settings page in the Salesforce setup menu.

If Realtime merge is required then set the App Setting “Is Realtime Merge Active?” to TRUE.

If Scheduled merge is required then set the App Setting “Is Realtime Merge Active?” to FALSE and schedule the Merge Job to perform scheduled merges. This process is completed via the steps below.

• Guided Setup > Schedule the Merge Job (setup action on the first screen)

Or,

• Open the Apex Classes page in the Setup menu.
• Click the “Schedule Apex” button.
• Select the required class (e.g. AccountMergeJob, LeadMergeJob:), define the Frequency and click the Save button.
• The Merge Job Schedule Status component on the OneMerge Application Home page displays the next scheduled execution time for each Merge Job.

Further help and Training Articles can be found here.

OneMerge provides bulk Matching Jobs for the standard Salesforce objects (Account, Contact, Lead and Person Account) which execute Salesforce Matching Rules in bulk across either all records in the object, or records which meet specific filter criteria.

OneMerge Matching Jobs enable a scheduled match and merge bulk record lifecycle ideal for the initial processing of data or where bulk data integration activities perform scheduled updates.

The Matching Job Filter configuration is managed via the Guided Setup link shown in the page footer of the OneMerge app, this is our recommended approach. Alternatively, the configuration can also be managed in the Custom Metadata Type of the same name which is accessible via the Salesforce setup menu or the Merge Ruleset Status panel displayed on the Home tab of the OneMerge app.

Matching Jobs are scheduled as per Merge Jobs (please see Step 6).

Further help and Training Articles can be found here.