Data and Analytics Management17% of the exam
Duplicate, matching and validation rules
How matching rules and duplicate rules work together to alert, block or report on duplicates at save time, and how validation rules enforce data standards, where their errors appear, how to exempt a user, and where they run in the save order.
Describe the capabilities and implications of data validation tools (duplicate and matching rules, validation rules).
~8 min read · 9 practice questions ·
What the exam expects
- Explain how a duplicate rule depends on an active matching rule, and diagnose why duplicates still get saved.
- Choose the duplicate rule action (allow with an alert, block, report) and scope (same object or cross-object, custom fields, conditions) for a requirement.
- Pick an exact or fuzzy matching method for a field, and know what duplicate management does not do (it never merges or deletes records on its own, and it does not clean up existing data at activation).
- Write a validation rule that fires conditionally, place its error message on the right field, and exempt a specific user with a custom permission.
- Predict how validation rules interact with other save-time logic such as before-save flows and API loads.
Key facts
Duplicate rule prerequisite
- Detail
- Every matching rule it uses must be active
Matching rule activation
- Detail
- Takes time; email sent when ready
Fields per matching rule
- Detail
- Up to 10
Active duplicate rules per object
- Detail
- Up to five
Matching rules per duplicate rule
- Detail
- Up to three
Duplicate rule actions
- Detail
- Allow (alert, report) or Block
Duplicates shown in Lightning alert
- Detail
- Up to 15
When duplicate rules run
- Detail
- On create or edit, not retroactively
Fuzzy: Company Name
- Detail
- Strips words like Inc and Corp before comparing
Validation formula result
- Detail
- True means invalid, save stopped
Error location
- Detail
- Top of Page or a specific field
Validation rules and the API
- Detail
- Apply to API and integration saves too
Before-save flow timing
- Detail
- Runs before custom validation rules
Sources for this section (8)
- Customize Duplicate Ruleshelp.salesforce.com (opens in a new tab)
- Customize Matching Ruleshelp.salesforce.com (opens in a new tab)
- Things to Knowhelp.salesforce.com (opens in a new tab)
- Stop Duplicate Recordshelp.salesforce.com (opens in a new tab)
- Matching Methodshelp.salesforce.com (opens in a new tab)
- Validation Ruleshelp.salesforce.com (opens in a new tab)
- Validation Rules Fieldshelp.salesforce.com (opens in a new tab)
- Order of Executiondeveloper.salesforce.com (opens in a new tab)
- What must be true of a matching rule before a duplicate rule that uses it can be activated?
- Why can an exact matching rule miss "Acme Inc." versus "Acme Incorporated"?
- When do duplicate rules evaluate a record, and what happens to duplicates that already exist?
- How do you let one integration user skip a validation rule while it stays active for everyone else?
- Why does a validation rule see a value the user never entered?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform Administrator pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 28 lessons of the Platform Administrator guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (9 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams