Dataverse uses duplicate detection rules to compare selected columns, such as Name, Email, or Phone, and identify possible duplicate records.
Before it works, duplicate detection must be enabled at three levels: organization, table, and operation (create/update).
It can be triggered by:
- Create or update: Dataverse checks the record and can show a duplicate warning.
- Scheduled duplicate detection jobs: Scans existing records for possible duplicates.
- Web API/SDK: Duplicate detection is suppressed by default. The request must explicitly enable it using SuppressDuplicateDetection = false.
Example: A rule compares Email addresses. If john@CoyLix.com already exists, creating another record with the same email can trigger a duplicate warning.
Interview tip: Remember that duplicate detection identifies possible duplicates; it doesn’t automatically prevent them.
