Preventing Duplicate Rows in Dataverse Tables
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. A company uses a Dataverse environment. The environment is accessed from canvas and model-driven apps. The Dataverse environment contains a table that has the following columns: • Name • Company • Contacted On The company requires that the table not contain any duplicate rows when users create data in the environment. You need to implement a solution that meets the requirement. Solution: Create a duplicate detection rule for the columns. Does the solution meet the goal?
Community Votes
80% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests the distinction between a warning mechanism (Duplicate Detection) and an enforcement mechanism (Alternate Keys). The trap is assuming that 'detecting' duplicates automatically stops the user from saving the record.
This question tests the capability of Microsoft Dataverse duplicate detection rules versus alternate keys for enforcing data integrity. The solution fails because detection rules only warn users, whereas the requirement demands preventing duplicate creation.
Candidates often choose 'Yes' because they believe Duplicate Detection Rules block saves, but these rules merely display a warning dialog allowing the user to proceed or cancel.
Community Discussion (7 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The correct answer is B (No). The requirement is to ensure the table does not contain any duplicate rows when users create data. A Duplicate Detection Rule in Dataverse identifies potential duplicates and presents a warning to the user, but it does not prevent the record from being saved. The user can override the warning and save the duplicate record anyway. Therefore, this solution does not meet the strict requirement of preventing duplicates.Why the Other Options Are Wrong
Option A (Yes) is incorrect because it assumes the rule acts as a hard constraint. In reality, "Duplicate Detection" is a soft check. To strictly enforce uniqueness, you must use Alternate Keys, which are system-enforced unique constraints that throw an error if a duplicate is attempted. Since the proposed solution lacks this enforcement, it is insufficient.Community Comment Notes
Community consensus strongly supports option B. As one commenter noted, "Only Alternate Keys can do that," highlighting the enforcement gap. Another user pointed out that duplicate detection rules may not even function correctly in Canvas apps, stating it "Doesn't work in canvas apps only in model driven." This reinforces that the solution is flawed both in its lack of enforcement and its limited scope across app types.Official Reference
Exam Strategy
When a requirement states 'prevent', 'block', or 'ensure no duplicates', look for Alternate Keys or Unique Constraints. If the option suggests 'Duplicate Detection', remember it is a warning feature, not a blocking feature, unless specifically configured with other plugins.
Frequently Asked Questions
Why doesn't Duplicate Detection stop duplicates?
It displays a warning dialog but allows the user to click 'Save Anyway'. It is a advisory tool, not an enforcement constraint.
How to strictly prevent duplicates in Dataverse?
Use Alternate Keys. They act as unique constraints and will throw a runtime error if a duplicate value is submitted, blocking the save.