PL-500 · Question #34
You are creating a solution that will use a Choice field for approvals. You need to ensure that other users can use the Choice field with their Microsoft Dataverse tables. What should you use?
The correct answer is A. Global choice. To trigger a Dataverse flow only when a record is added and two specific conditions are met, you must use an '@and' logical operator that combines 'equals' checks for both the website URL and the underlying integer value of the 'Yes' option for the choice field.
Question
You are creating a solution that will use a Choice field for approvals. You need to ensure that other users can use the Choice field with their Microsoft Dataverse tables. What should you use?
Options
- AGlobal choice
- BLocal choice
- CEnvironment variable
How the community answered
(29 responses)- A93% (27)
- B3% (1)
- C3% (1)
Why each option
To trigger a Dataverse flow only when a record is added and two specific conditions are met, you must use an '@and' logical operator that combines 'equals' checks for both the website URL and the underlying integer value of the 'Yes' option for the choice field.
The trigger condition requires both specified conditions to be true, so the `@and` function is correct. Dataverse Choice fields, such as `crabd_triggerflow`, store selected options as integer values (e.g., 'Yes' commonly maps to '126690000'), and the `websiteurl` comparison requires an exact string match for 'https://microsoft.com'.
This option uses `126690001` for the `crabd_triggerflow` field, which typically corresponds to 'No' or a different option in a Dataverse Choice field, not 'Yes'.
This option uses the `@or` operator, which would trigger the flow if *either* condition is true, not *both*, contradicting the requirement for an 'AND' condition.
Concept tested: Power Automate Dataverse trigger conditions with Choice fields
Source: https://learn.microsoft.com/en-us/power-automate/create-flow-with-dataverse-trigger
Topics
Community Discussion
No community discussion yet for this question.