This month, we're releasing a new interface for the bulk merge tab, along with a few teasers of what we're working on, so you can give us feedback. We've also fixed a handful of minor issues and made some improvements.
Release Schedule
Monday, June 1 - Available on the AppExchange, pushed to all sandboxes
Wednesday, June 3 - Pushed to all orgs
Release Notes
New Bulk Merge UI
We've simplified the bulk merge view and rearranged a few things in preparation for upcoming features. If you're interested in any of them, please click on the feature you want, sign up for early access, and we will add you to the beta programs as they're ready. This also includes a few improvements available now:
Lookup fields now show the name of the related record instead of the ID.
We fixed the scrolling so you don't have to scroll all the way back up to start a merge.
The duplicate rule dropdown now indicates which duplicate rules are inactive. They will only show up if there are duplicates from that rule.
We fixed an issue where the number of duplicates was not showing in orgs with more than 50,000 duplicates (yes, these orgs exist, and we've seen them!).
Field Handling
We've fixed a few issues with how we handled certain fields.
Lookup fields now show the name of the related object on the bulk merge tab instead of the ID.
We've made encrypted field handling consistent and secure. Before, it would show encrypted values on bulk merge even if you didn't have permission.
We've fixed how automerge works when merging multiple records into a record with a blank value. Previously, if you had chosen an Automerge rule like "newest record," but the newest record had a blank value, it would arbitrarily take a value from another record. Now it will take the value from the second newest.
We fixed the formatting of currency fields to ensure consistency across all screens.