Brent Downey has created a brilliant post on Salesforce’s new “Duplicate Management” tool. But one of the obvious features that is missing is being able to change the columns that the user sees when the Duplicate Management finds a match. For example, if you are matching on (e.g.) the contact name and city, when you find matching records only the contact name and city are displayed in the matching table, and there is no option to change this, which can be a real pain! I want to see the company name, address, etc. So I can tell if an actual duplicate or not. But there is a solution that I mentioned in my “Data Tips, Tricks & Strategy” session at Dreamforce 2015.
Fake your Matching rule
Brent did a great post on how to setup Duplicate Management, but I’m just going to focus on the matching rule. Based on my example above if I wanted to create a matching rule to match contacts with a similar First Name and Last Name I would create a matching rule that looks like the following:
Duplicate Management > Matching Rule; Matching on Contact First name & Last name
The Problem
The problem with this rule is when it is displayed to the user ONLY the First name, Last name & Last name is displayed of the matching contacts. Which is a real pain because it doesn’t give you enough information to see if the person just happens to have the same name. I want to see the address information of that contact, which city they are in, company name, maybe their email address
What the user sees on a Matching Rule using First name & Last name
The Solution
The solution to this is to fake your matching rule. If the field is in the matching rule, it is displayed to the user. So you need to follow this logic:
(<your matching rule>) OR ((<your matching rule>) AND <fieldYouWant> AND <fieldYouWant> AND <...>)
So If I wanted to see the contacts Account name, Email & Mailing City I would do the following:
The fake matching criteria added on to the end of our original matching rule
The additional OR criteria doesn’t effect the original rule (that the First name and Last Name must match); it just adds in the other fields creating a fake rule that doesn’t make any sense at all. If 1 AND 2 match then the rule will never evaluate the “1 AND 2 AND 3 AND 4 AND 5”. SO when the user now sees the match they get the following:
What the user sees using the fake matching rule
So now they see all the columns that you want them to see when a record is matched!