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 ·
The pack unlocks every unit in the guide, reading progress, one-click practice for each topic (9 questions for this one), and unlimited timed mock exams.
| Fact | Detail | Source |
|---|---|---|
| Duplicate rule prerequisite | Every matching rule it uses must be active | |
| Matching rule activation | Takes time; email sent when ready | |
| Fields per matching rule | Up to 10 | |
| Active duplicate rules per object | Up to five | |
| Matching rules per duplicate rule | Up to three | |
| Duplicate rule actions | Allow (alert, report) or Block | |
| Duplicates shown in Lightning alert | Up to 15 | |
| When duplicate rules run | On create or edit, not retroactively | |
| Fuzzy: Company Name | Strips words like Inc and Corp before comparing | |
| Validation formula result | True means invalid, save stopped | |
| Error location | Top of Page or a specific field | |
| Validation rules and the API | Apply to API and integration saves too | |
| Before-save flow timing | Runs before custom validation rules |