Hi, I am working on managing duplicate records on a custom object that contains very few fields :
- Two Master-Detail fields (Account, Contact)
- Some Formula fields
- and the usual standard fields (created by, last modified...)
I know that Formula fields and the standards fields are not supported in the matching rule. Also, I know that a matching rule can only have one lookup relationship field, but we actually only use these two M-D fields to create a record.
Salesforce asks to add another field for the matching rule, but no other fields are supported/available for the matching rule.
Have you faced similar issue? Thanks
Hi @John C ,Hope your issue was resolved!
I faced a similar issue, as org’s matching criteria allow only one lookup field per Matching Rule.
So, you cannot include both Account and Contact lookup fields in a single matching rule.
A possible workaround would be to create two separate Matching Rules for the junction object(which has 2 M-D relationship fields) , one using the Account lookup field and another rule using the Contact lookup field and associate both rules with the same Duplicate Rule
(Click add rule in Duplicate Rule ) configured to block duplicates.
Ensure that both Matching Rules are activated for the Duplicate Rule.
One important consideration is the business requirement:
- If the goal is to prevent duplicate Account-Contact combinations, both fields must match the existing record.
- If the goal is to prevent either Account or Contact from appearing more than once, the matching logic would be different.
Note that using two separate Matching Rules may not enforce the first requirement by itself, so test the configuration to ensure it behaves as intended.
Thanks!!
