Apex Global is setting up duplicate handling on the Account object. The operations team requires that when sales representatives manually create duplicate Account records, Salesforce should warn the user and log the entry in a duplicate record report without preventing creation. Conversely, when external system integrations insert Account records via the API under an Integration User profile, duplicate creation must be strictly prevented. Which TWO configurations within Salesforce Duplicate Management are required to fulfill these business requirements?
- Configure a Duplicate Rule with the Action on Create set to Allow, selecting both the Alert and Report options.Cevap
- Configure a separate Duplicate Rule with Rule Conditions filtering for the Integration User profile that sets the Action on Create to Block.Cevap
- CConfigure the underlying Matching Rule criteria to enforce a Block action when the record insertion origin is identified as API.
- DDeactivate the Matching Rule for the Integration User profile to trigger automated system blocking during bulk record creation.
Cevap
The administrator must configure a Duplicate Rule with Action on Create set to Allow (with Alert and Report enabled) for manual record creation, and configure a second Duplicate Rule using Rule Conditions for the Integration User profile with Action on Create set to Block.
In Salesforce Duplicate Management, Matching Rules define the criteria used to identify duplicate records (e.g., matching Account Name and Billing Address). Duplicate Rules determine the outcome when duplicates are detected. Setting Action on Create to Allow with Alert and Report allows users to proceed after seeing a prompt while logging the activity. Adding Rule Conditions to a Duplicate Rule allows administrators to enforce a strict Block action specifically for automated integration profiles.
Adım Adım Çözüm
Anahtar Kavram
Matching Rules define duplicate identification criteria, while Duplicate Rules enforce action responses (Allow, Block, Alert, Report) and execute conditional evaluation logic based on user criteria.