PL-200 · Question #273
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. A Power Automate flow with an 'Update a row' action does not meet the goal because flows execute asynchronously and cannot guarantee real-time, synchronous updates to a Status column in a model-driven app.
Question
Options
- AYes
- BNo
How the community answered
(17 responses)- A24% (4)
- B76% (13)
Why each option
A Power Automate flow with an 'Update a row' action does not meet the goal because flows execute asynchronously and cannot guarantee real-time, synchronous updates to a Status column in a model-driven app.
This solution does not meet the goal because Power Automate flows are inherently asynchronous and cannot update the Status column synchronously in the same transaction as the triggering action.
Although 'Update a row' is the correct Dataverse connector action in Power Automate (unlike 'Update item' which targets SharePoint), Power Automate flows still run asynchronously in the background after the triggering event. This means there is a delay between the trigger and the column update, which does not satisfy the real-time requirement. A synchronous classic Dataverse workflow is needed for true real-time updates.
Concept tested: Asynchronous Power Automate vs real-time Dataverse workflow
Source: https://learn.microsoft.com/en-us/power-automate/dataverse/overview
Topics
Community Discussion
No community discussion yet for this question.