--- schema_version: "1" id: a40d95752975ee278f1612b19015827f56398d552f74b7440687e534d798320f title: Things to Know About Duplicate Rules collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/duplicate_rules_overview.md canonical_url: https://help.salesforce.com/s/articleView?id=sales.duplicate_rules_overview.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 10ac67329bb04a2cbc4c3aa9a63ee214a52b6fc06300f5d2e9856eeccfb5e321 description: Review considerations for using and customizing duplicate rules. products: - Sales - Sales Enablement release: "264" --- # Things to Know About Duplicate Rules Review considerations for using and customizing duplicate rules. ### Required Editions
Available in: Lightning Experience and Salesforce Classic
Available in: Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions
Number of Duplicate and Matching Rules - You can use up to five active duplicate rules per object. - You can add up to three matching rules in each duplicate rule, with one active matching rule per object. When you use multiple duplicate rules, you can include up to five active matching rules per object. Duplicate Record Sets Generated by Selecting the Report Option If you select the Report option for duplicates identified using a duplicate rule, and a user saves a record identified as a duplicate, the following happens. - The saved record and the maximum number of duplicates are reassigned to a new or existing duplicate record set. For each matching rule run on a record, up to 100 duplicates can be reassigned to a duplicate record set. A matching rule can be associated with a duplicate rule or a duplicate job. - The saved record and each of its duplicates are listed as duplicate record items in the duplicate record set. - If the duplicate rule looks for duplicates across objects (for example, contacts that duplicate leads), the duplicate record set includes duplicates on the other objects. If a duplicate lead is converted before the duplicate record set is created, the duplicate record set doesn’t include the converted lead. Records with More Than 100 Matches Match keys help to increase the performance of duplicate rules through a preliminary comparison that narrows the matches to the 100 most likely duplicate records. Then the rule applies the matching equation only to those likely matches. Impact of User Access on Rules If a user who updates a record doesn’t have access to one or more fields referenced in a matching rule, then the duplicate rule doesn’t work as expected. For example, suppose that standard users don’t have access to the account name field. Then an admin creates a matching rule that depends on the field. If an admin updates a record, the duplicate rule runs as expected. But when a standard user updates the same record, the rule doesn’t identify duplicates. How Rules Operate on Edited Fields You can configure a duplicate rule to perform an action when a record is created or edited. However, the rule only runs on edited records when the edited fields are included in the associated matching rule. For example, if a sales rep edits a custom field, the rule doesn’t run unless you’ve created a matching rule that includes the custom field. Global Picklist Value Sets Global picklist values aren’t supported in duplicate rules. Custom Picklists Custom picklist fields aren’t supported in matching rules used in cross-object duplicate rules. For example, you can’t use a custom picklist field on the lead object in a rule that matches contacts which duplicate leads. Changes to a Rollup Summary Field Value When a rollup summary field value changes, duplicate rules run, and the Allow option (to save a duplicate record) isn’t supported. Conditions Under Which Duplicate Rules Don’t Run - Records are created using Quick Create or Community Self-Registration. - Leads are converted to accounts or contacts, and **Use Apex Lead Convert** isn’t enabled. - Records are restored with the Undelete button. - Records are added using Lightning Sync or Einstein Activity Capture. - Records are manually merged. - A Self-Service user creates records, and the rules include conditions based on the User object. - Duplicate rule conditions are set for lookup relationship fields and records but no value for these fields has been saved. For example, a condition specifies that a duplicate rule runs when a campaign doesn’t contain “Salesforce.” If you then add a record with no value for the Campaign field, the duplicate rule doesn’t run. Conditions Under Which Duplicate Rule Settings Are Overridden In the following situations, no alert is shown and users can’t save records. - Records are added using the data import tools. - A person account is converted to a business account, and the newly created business account matches an existing business account. - Records are added or edited using Salesforce APIs. Timing of Saves Suppose that multiple records are saved simultaneously and your duplicate rule is set to block or alert sales reps. The records aren’t compared with each other. They’re compared only with records already in Salesforce. This behavior doesn't affect the Report option, and duplicate record sets do include records that match other records saved simultaneously. Translation Workbench The Translation Workbench doesn’t support the customizable alert text in duplicate rules. #### See Also - [Manage Duplicates Using Duplicate Record Sets](https://help.salesforce.com/s/articleView?id=sales.duplicate_management_duplicate_record_sets.htm&release=264.0.0&type=5 "A duplicate record set is a list of items identified as duplicates. It’s created when a duplicate rule or job runs. Let your Lightning Experience users merge duplicates by granting them access to duplicate record sets.") - [Create Reports on Duplicate Records](https://help.salesforce.com/s/articleView?id=sales.duplicate_management_custom_report_types.htm&release=264.0.0&type=5 "Use duplicate record reports to fine-tune your duplicate and matching rules and share the results of duplicate jobs.")