OneMerge Free Edition is available from the Salesforce AppExchange as a Preconfigured Trial Org or for installation into your own Salesforce Org (sandbox or production). OneMerge Free Edition Trial Org licenses are activated for 7 days.
The notes below provide additional trial support information including 2 simple-to-follow test cases for Preconfigured Trial Orgs which demonstrate how OneMerge works.
Please get in touch if we can help at all with the trial setup or your evaluation process.
We offer a courtesy QuickStart call to all customers; on this call we’ll discuss your requirements and provide expert setup guidance. Where requirements are straightforward we aim to configure the product with you on the call.
Contact us via the Contact Page or via Email.
OneMerge Free Edition is available via our Salesforce AppExchange listing in 2 ways;
(1) Preconfigured Trial Org (7 day license).
A preconfigured trial which includes the test records referenced in the exemplar test scenarios below.
(2) Installation into your Org.
Please install via the AppExchange listing. Alternatively, our Release Notes page provides the package version installation link for each versioned release.
Once the app is installed please review the Post Installation instructions.
The notes below relate specifically to the configuration of the Preconfigured Trial Orgs provisioned from the OneMerge Free Edition AppExchange listing.
1. Duplicate Management.
Standard Matching Rules are activated (Person Account, Account, Contact and Lead).
Standard Duplicate Rules are activated (Person Account, Account, Contact and Lead).
Note: all Duplicate Rules are configured with the Report option ticked for both Operations On Create and Operations On Edit; this is mandatory for OneMerge merge automation.
2. OneMerge Free Edition Merge Configuration.
The out-of-the box merge configurations (i.e. Merge Rulesets) for the standard objects are unaltered. The exception to this is Lead where the Gender Identity and Pronouns fields have been added to the standard Name Merge Rule.
3. Salesforce Configuration.
The OneMerge App has been set as the default for the System Administrator profile.
The following example test scenarios are provided to help with the trial evaluation process. Please note that the test records referenced are created by default in Preconfigured Trial Orgs only.
Scenario 1. Scheduled merge for duplicate Person Accounts.
1.1. Open the Sophie Grigson Person Account test record.
You can see that this record has not previously merged as the “Is Merge Master?” flag is false (OneMerge Information section).
You can see that the Mobile number is +12126348059.
Important. Please save the record to generate the Match Key used by Salesforce Matching Rules. This step is required as the keys are missing by default on existing records generated in trial Salesforce orgs.
1.2. Create a new duplicate Person Account record as below.
Name = Sophie Grigson
Email = sophie.grigson@trial.onemerge.co.uk
Mobile Phone Number = +12126348060
You should see a Duplicate alert, this can be ignored. The alert is shown by Salesforce Duplicate Management which is configured to Alert and Report new duplicates, The former provides the UI notification the latter generates a Duplicate Record Set which OneMerge processes.
Click Save.
1.3. [Optional] View the Duplicate Record Set generated by Salesforce Duplicate Management.
Open the Duplicate Record Sets tab in the OneMerge app. A new Duplicate Record set should be visible; this represents the reported duplication between the original and new “Sophie Grigson” records. OneMerge Free Edition processes Duplicate Record Sets and merges the duplicate records.
1.4. View the Home page.
Within the OneMerge app open the Home page and view the Merge Job Status panel to determine the next scheduled run time for the Person Account Merge Job.
If there is no scheduled Merge Job for Person Accounts, please create one via the Guided Setup link in the footer (utility) bar. For Person Accounts select the Account object and enter PersonAccount as the sub type on the first page. The scheduled job can be set to run with Schedule Type=Now for convenience.
Once the Person Account Merge Job next run time has passed please proceed to step 1.5.
1.5 Open the original Sophie Grigson Person Account test record.
The Mobile Phone Number has now changed to the value from the duplicate (as the most recent value), the Last Merged Date timestamp should also be updated. The Merge Rule Lineage component (as shown below) can be used to view the prior Mobile Phone Number value and also to navigate to the Merge Result record which records the details of the merge event.
Note, the duplicate record has also been deleted by the merge event. Free Edition uses the Salesforce merge function which deletes losing records. OneMerge Standard Edition (and above) provides a custom merge engine which allows losing records to be retained and linked to the master record allowing future data changes to be synchronised.
1.6. Rollback the Merge.
Open the Merge Result record via the Merge Results related list or the links within the Merge Rule Lineage component; both are shown above.
On the Merge Result page click the Rollback button, displayed top-right, and complete the Rollback process by clicking the Next button.
Once rollback is complete the page is returned to the original Sophie Grigson Person Account test record; you can see that the previous merge related changes have now been reverted and the original Mobile Phone Number value +12126348059 restored.
Scenario 2. Scheduled merge for duplicate Leads.
2.1. Open the Sarah Loehr Lead test record.
You can see that this record has not previously merged as the “Is Merge Master?” flag is false (OneMerge Information section) and the “Merge Rule Lineage” component is not visible.
You can see that the Street is Two Jones Avenue.
(Important. Please save the record to generate the Match Key used by Salesforce Matching Rules. This step is required as the keys are missing by default on existing records generated in trial Salesforce orgs. You will need to enter the Company Name ‘MedLife’ before saving.)
2.2. Create a duplicate Lead record as below.
Name = Sarah Loehr
Company = MedLife
Email = s.loehr@trial.onemerge.co.uk
Street = One Jones Avenue, City = New York, State = NY and Zip = 10010, Country = USA
You should see a Duplicate warning, this can be safely ignored.
Click Save.
2.3. [Optional] View the Duplicate Record Set generated by Salesforce Duplicate Management.
Open the Duplicate Record Sets tab in the OneMerge app. A new Duplicate Record set should be visible; this represents the reported duplication between the original and new “Sarah Loehr” records. OneMerge Free Edition processes Duplicate Record Sets and merges the duplicate records.
2.4. View the Home page.
Within the OneMerge app open the Home page and view the Merge Job Status panel to determine the next scheduled run time for the Lead Merge Job.
If there is no scheduled Merge Job for Leads, please create one via the Guided Setup link in the footer (utility) bar. Once the Lead Merge Job next run time has passed please proceed to step 2.5.
2.5 Open the original Sarah Loehr Lead test record.
The Street, has now changed to the value from the duplicate (as the most recent), the Last Merged Date timestamp should also be updated. The lineage component can be used to view the prior field values and also to navigate to the Merge Result record which records the details of the merge event.
Note, the duplicate record has also been deleted by the merge event.