Potential Duplicates Component
The Potential Duplicates component can be placed on a record detail page for standard or custom objects. It provides real-time duplicate detection based on selected matching rules.
Overview
The component allows you to:
- View existing duplicates directly on the record page
- Merge duplicates together without leaving the record
- Support cross-object matching including lead conversion
Adding the Component
To add the Potential Duplicates component to a record page:
- Navigate to the record detail page where you want to add the component
- Click the Edit Page button to open Lightning App Builder
- Drag the Potential Duplicates component onto the page
- Save and activate the page
- After the page is active, click the gear icon on the component to select matching rules
Configuration
Matching Rules Selection
Click the gear icon on the component to select matching rules:
- Up to 5 matching rules can be selected
- Only 1 matching rule with cross-objects matching is allowed
- Select rules that are most relevant for the object type
- Rules are evaluated in real-time when the record page loads
Per-Object Setting: Selected matching rules are saved per object, not per Lightning record page. If you configure rules for Contact, the same rules will apply on all Contact record pages where the component is placed.
Best Practice: Select matching rules that are specifically designed for the object type on which the component is placed. For example, use Contact-specific matching rules on Contact record pages.
Use Cases
The Potential Duplicates component is useful for:
- Real-time duplicate detection – See potential duplicates immediately when viewing a record
- Quick merge actions – Merge duplicates without navigating away from the current record
- User-friendly interface – Provide duplicate detection directly in the user's workflow
- Cross-object matching – Detect duplicates across different object types (e.g., Lead and Contact)
Important Notes
Results May Vary: The Potential Duplicates component may show different results compared to the duplicate reports. This is because:
- The component uses real-time matching when the page loads
- Reports may use cached or scheduled results from previous matching rule runs
- Different matching rules may be applied in the component vs. reports
Limits:
- Up to 5 matching rules can be selected per component
- Only 1 matching rule with cross-objects matching is allowed
- The component evaluates duplicates in real-time, which may impact page load performance for large datasets
Performance: For better performance, limit the number of matching rules and avoid selecting rules that process large volumes of records.
Read Only Access: Users with the No Duplicates Read Only permission set will not see the Merge button or the gear icon to select matching rules.