A Salesforce Administrator needs to configure automated duplicate control for a custom object named Financial Account. The solution must block creation of duplicate records based on custom matching criteria and report duplicates when records are updated. In what exact order should the administrator perform these steps to successfully configure, activate, and verify the duplicate management setup?
- 1Create a custom Matching Rule on the Financial Account object by defining field criteria, matching algorithms (exact/fuzzy), and matching logic.
- 2Activate the custom Matching Rule so Salesforce can generate the required matching keys.
- 3Create a Duplicate Rule on the Financial Account object, associate the activated Matching Rule, set Action on Create to Block, and set Action on Edit to Allow with Report selected.
- 4Activate the Duplicate Rule to enforce duplicate checking during user and API operations.
- 5Attempt to create a duplicate record in the user interface to verify that record creation is blocked and an alert message is presented.
Answer
The correct operational sequence is: 1) Create the custom Matching Rule, 2) Activate the Matching Rule to compile matching keys, 3) Create the Duplicate Rule referencing the active Matching Rule and configuring Block/Report actions, 4) Activate the Duplicate Rule, and 5) Test record creation to verify enforcement.
The configuration of Salesforce Duplicate Management follows a strict dependency hierarchy: Matching logic must be defined (Matching Rule) and indexed (Matching Rule Activation) before enforcement rules can consume it (Duplicate Rule Creation & Activation), followed by end-to-end verification (Testing).
Step-by-Step Solution
Key Concept
Salesforce Duplicate Management Lifecycle & Key Indexing