PL-200 · Question #303
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…
The correct answer is B. No. The proposed solution, likely involving an insufficient uniqueness configuration, does not prevent duplicate rows if it fails to consider both 'Name' and 'Company' in combination.
Question
Options
- AYes
- BNo
How the community answered
(40 responses)- A25% (10)
- B75% (30)
Why each option
The proposed solution, likely involving an insufficient uniqueness configuration, does not prevent duplicate rows if it fails to consider both 'Name' and 'Company' in combination.
If the solution focused on a single column (e.g., 'Contacted On') or an incomplete combination for uniqueness enforcement (e.g., only 'Name'), it would not prevent duplicate entries for the same 'Name' and 'Company' if other fields differ, thereby failing the requirement to prevent duplicate rows.
Concept tested: Dataverse alternate key design for uniqueness
Source: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/define-alternate-keys-reference-rows
Topics
Community Discussion
No community discussion yet for this question.