Power Platform Community Forum Thread Details

Power Automate Flow Not Triggering when a Field in a Dataverse row Change

Hi everyone,

I’m working on a model-driven app with data saved in Dataverse and trying to set up an automation workflow using Power Automate. Here’s the setup:

I have a flow in the Dev environment with a trigger "When a row is added, modified, or deleted" (change type: modified) on the Projects table.
I’m specifically monitoring a formula text based column called new_projectfinishedandreadytocloseoutcheck, and I set a 'filter rows' condition: "new_projectfinishedandreadytocloseoutcheck eq 'Yes'".
I also set 'Triggering Condition' as '@equals(triggerOutputs()?['body/new_projectfinishedandreadytocloseoutcheck'], 'Yes')'
The idea is for the flow to start when this field changes from "No" to "Yes."

r/MicrosoftFlow - Power Automate Flow Not Triggering when a Field in a Dataverse row Change

However, when I test this by changing the field value in Power Apps in Dev environment, the flow doesn’t trigger. Does anyone have experience troubleshooting this or have suggestions on what to check next?

I’m also wondering if there’s something I might be missing in terms of Dataverse permissions for my Dev environment, or if there are specific security settings needed to trigger a flow based on field changes. I am 'system administrator' role.

Thanks in advance!

Categories:

Business Process Flows

I do not have a solution for you. I just wanted to let you know that I am having the same issue. I created the flow in another environment that I have, and this trigger worked without any issues. The environment where it did not work was created within the last month whereas the environment where it did work was created more than two years ago. Was your environment recently created? If so, it may be a clue as to the problem and require a ticket to be opened with Microsoft.

Although the issue for you might be your trigger condition. Try updating 'Yes' to 1 without quotes instead. With yes/no, true/false fields, 1 is usually yes/true and 0 is no/false.

So far, we cannot see any configuration differences between the environment where it works and the one where it does not.

Quick Links

Leaderboard