You are here:
Things to Know Before You Customize Matching Rules
Review considerations for customizing matching rules.
Required Editions
| Available in: Lightning Experience and Salesforce Classic |
| Available in: Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions |
| Consideration | Description |
|---|---|
| Limits |
|
| Order of Evaluation of Certain Fuzzy Matching Method Segments | Suppose the following: a matching rule includes a filter with logic that includes an OR operator, and the segments before and after the operator include the same field with a fuzzy matching method. The rule evaluates only the filter segment closest to the end, and ignores the others. As another example, suppose that a filter criterion has 1 = account name (fuzzy), 2 = address (exact), 3 = phone (exact), and 4 = zipcode (exact). If filter logic is (1 AND 2) OR (1 AND 3) OR (1 AND 4), the rule evaluates only (1 AND 4) and ignores both (1 AND 2) and (1 AND 3). If filter logic is (1 AND 2) OR (1 AND 3) OR (1 AND 4) OR (2 AND 4), the rule evaluates (1 AND 4) OR (2 AND 4). Both (1 AND 2) and (1 AND 3) are ignored. To avoid skipped logic, create a matching rule for each OR segment that includes the same fuzzy fields. Use either fuzzy or exact matching. Duplicates aren’t detected if you include both matching types in one rule. |
| International Data | Standard and custom matching rules that use fuzzy matching methods support only Latin characters. If you're using international data, we recommend using the exact matching method with your matching rules. |
| Lookup Fields | If the value of a lookup field is a person account and the matching rule includes a contact lookup field, the matching rule isn't applied. All contact lookup fields, except Reports To on the Contact object, contain both contacts and person accounts. You can configure a lookup filter to exclude person accounts. To match on person account values, use an account lookup field instead. |
| Records in Hierarchies | If the record chosen as primary is below another selected duplicate in a hierarchy, you can't finish merging. Choose a different primary record or edit the Parent Account or Reports To value on one of the records. |
| Fields That Become Unavailable | If a field on an object is no longer available in your org, it can cause matching rules with mappings to this field to be ignored. When the fields in your org change, check all duplicate rule field mappings for an object. |
| Shield Platform Encryption | Standard and custom matching rules that include fields with Shield Platform Encryption detect duplicates as long as those fields are encrypted deterministically. Probabilistic encryption isn't supported. When you rotate your key material, you must update custom matching rules that reference encrypted fields. After you rotate your key material, deactivate and then reactivate the affected matching rules. Then contact Salesforce to request the background encryption process. When the background encryption process is finished, your matching rules can access the data encrypted with your active key material. Service protections ensure that loads are balanced across the system. The matching service searches for match candidates until they find all matches or up to 200 matches. With Shield Platform Encryption, the service search maximum is 100 candidates. With encryption, you could find fewer or no possible duplicate records. Duplicate jobs aren't supported. |
