Unanswered

Flow with a Dataverse trigger 'When a row is added, modified or deleted'

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

I have created a flow that triggers when a Dataverse row is added or modified with scope of User. It is triggering constantly, like every couple of seconds. I assume there is a process in Dataverse that is constantly updating the table? I only want it to be triggered when a row is added/modified by a user.

Categories:

Using flows

I have the same question (0)

All responses (4)

Answers (0)

Sort by

ArchitectMadhan 1,584 on at

Like (1)

Report
Copy link

Link copied!

Hi @Anonymous ,

In your case, it might have triggered for all the field update or create. Please make sure you use the trigger condition based on which field update you need to trigger the flow.

In the below trigger condition, I have just used the status field is true.

Based on the above condition the flow will be triggered, if only the status is 1 (on updating the status field). you can also use multiple fields as well.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @ArchitectMadhan, thanks for your reply. Thinking about this again I believe it is constantly firing because the flow itself is modifying the same record, like a circular reference. I need a way to run a flow once when a record is added/modified and to be able to update the same record within the flow.

Was this reply helpful? Yes No
v-jefferni Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hi @Anonymous ,

Could you please share more details about your flow? Are you using an Update a row action in your flow, which will cause infinite loop?

Best regards,

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hi @v-jefferni, you are spot on, the flow was updating a Dataverse row and would re-trigger the flow in an infinite loop.
I have read suggestions around having an additional column and then a trigger condition to test that value
@equals(triggerBody()?['oss_updated'], 1) and setting the same column value in the update row to 0. But I see some risk here still if there is an error in the flow and the column doesn't get updated.
I am inclined to have the user run the flow manually from an Command button instead.

Was this reply helpful? Yes No