Skip to main content

Potential Duplicates v2.16

Minor improvements to the record component and bulk merge pages and handling for some unique merge scenarios.

Updated yesterday

This release contains makes merging easier with several small improvements that we've heard from users.

Release Schedule

  1. January 26, 2026 - Available on AppExchange and pushed to sandboxes.

  2. January 28, 2026 - Pushed to all orgs

Release Notes

Backup Your Data

Coinciding with this version, we're launching our new backup solution, DBSAVER! If you're tired of managing weekly exports or paying for overpriced backup tools that you rarely use, we recommend you check it out. We've been using this backup solution for over a decade to back up data for our consulting clients, and we've decided to open it up to everyone. It's a simple, cost-effective backup tool designed to do exactly what you need: backup your data frequently and easily.

When merging duplicates using Bulk Merge, you'll see the usual reminder to back up your data before merging, along with a link to DBSAVER. If you already have your backups handled, you can easily dismiss this message.

Display Count of Duplicates on Bulk Merge

Many people have requested this simple improvement to see how many duplicates and duplicate groups are left to clean up. This count updates as you switch objects, duplicate rules, or search for duplicates, so you can get a clear count for whichever data you're currently working on.

Avoid Circular Dependencies on Merge

Salesforce doesn't let you set a lookup field to the record itself. Which can cause a problem when you're merging related records. For example, if you merge an Account with its parent and it automatically copies the Parent Account value, you'll get an error. Now, the Automerge function automatically detects this and skips copying any value that would trigger the error.
​

Merge Images in Rich Text

When merging two records with rich text fields, even in Salesforce, the images may appear as "Image Not Available" after the merge. That is because the images are stored in related files, and the file references are not updated. The latest version now allows you to merge records with rich text fields and images.

Bug Fixes

  • We updated address handling in Automerge to treat the address as a whole. This avoids merging the country from one record into an incompatible address that was missing the country.

  • Fixed an issue where the duplicate search was running twice for Accounts in orgs where person accounts were enabled.

  • Added appropriate error handling if an admin enters the same field on the "Fields to Always Display" and "Fields to Hide" settings.

  • Fixed an issue where Billing/Shipping latitude was not carried over when merging addresses.

Did this answer your question?