An administrator at Borealis Energy created and activated a custom Matching Rule on the Account object using the Account Name and Tax ID fields. However, when sales representatives save new Account records containing values identical to existing accounts, Salesforce saves the records without displaying warnings, blocking creation, or generating entries in Duplicate Record Sets. Which of the following explains why duplicate records are still being created without any warning?
- The corresponding Duplicate Rule is inactive or lacks configured actions such as Alert or Report.Cevap
- BMatching Rules only evaluate records during scheduled batch jobs and do not execute during real-time record creation.
- CThe Matching Rule must be embedded within a Record-Triggered Flow to execute validation logic on save.
- DCustom fields used in Matching Rules require Apex triggers to enforce duplicate prevention logic upon record creation.
Cevap
The corresponding Duplicate Rule is inactive or lacks configured actions such as Alert or Report.
In Salesforce Duplicate Management, Matching Rules define *how* potential duplicates are identified (the criteria), whereas Duplicate Rules define *when* to run duplicate checks and *what action* to take (Alert, Block, Report). Activating a Matching Rule has no visual or reporting effect until an active Duplicate Rule uses it.
Adım Adım Çözüm
Anahtar Kavram
Separation of responsibilities between Matching Rules (identifying duplicates) and Duplicate Rules (enforcing actions).