Question
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 an alternate key for the columns.
Does the solution meet the goal?
- A. Yes Correct
- B. No
Explanation
An alternate key defined on the Name, Company and Contacted On columns makes Dataverse create a unique index on that combination. Once the key is active, the platform rejects any create or update that would produce a second row with the same values in those columns, whether the data comes from a canvas app, a model-driven app or an integration. Single line of text and Date and Time columns are both supported for alternate keys. Unlike duplicate detection rules, which only warn users and can be bypassed, an alternate key enforces uniqueness, so the solution meets the goal. Rows with blank (null) key values are not checked, so the key columns should be filled in.
