PL-500 · Question #33
You are developing a flow that interacts with a Microsoft Dataverse table named Account. The table includes the following columns: The flow must only trigger when a record is added to the Accounts…
The correct answer is A. @and(equals(triggerOutputs()?['body/crabd_triggerflow'], '126690000'). To ensure a Dataverse Choice field can be reused across multiple tables by various users, it must be defined as a Global choice, also known as a global option set.
Question
You are developing a flow that interacts with a Microsoft Dataverse table named Account. The table includes the following columns:
The flow must only trigger when a record is added to the Accounts table and the following conditions are met: the websiteurl field is set to https://microsoft.com the crabd_triggerflow field is set to Yes You need to configure the flow trigger. Which trigger condition expression should you use?
Exhibit
Options
- A@and(equals(triggerOutputs()?['body/crabd_triggerflow'], '126690000'),
- B@and(equals(triggerOutputs()?['body/crabd_triggerflow'], 126690001),
- C@or(equals(triggerOutputs()?['body/crabd_triggerflow'], 126690000),
- D@or(equals(triggerOutputs()?['body/crabd_triggerflow'], '126690001'),
How the community answered
(38 responses)- A74% (28)
- B8% (3)
- C16% (6)
- D3% (1)
Why each option
To ensure a Dataverse Choice field can be reused across multiple tables by various users, it must be defined as a Global choice, also known as a global option set.
A Global choice (global option set) in Dataverse is defined once at the environment or solution level, allowing it to be consistently reused by multiple Choice columns across different tables, which enables other users to utilize it with their own Dataverse tables.
A Local choice (local option set) is defined directly on a specific column within a single table and cannot be reused by other columns or tables, making it unsuitable for shared use.
An environment variable stores configuration values for a solution to be used across different environments, but it does not define reusable choice options for Dataverse columns.
Concept tested: Dataverse Global Choice (Option Sets)
Source: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-optionsets
Topics
Community Discussion
No community discussion yet for this question.