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 a business rule for the columns.
Does the solution meet the goal?
- A. Yes
- B. No Correct
Explanation
A business rule evaluates conditions and actions on the values of the current row only (whether scoped to a form or to the table), so it cannot look at other rows to check whether the same Name, Company and Contacted On values already exist. It therefore cannot prevent duplicate rows from being created from both canvas and model-driven apps. Uniqueness across a set of columns is enforced with an alternate key defined on those columns, which Dataverse checks on every create or update regardless of the app used. The solution does not meet the goal.
