Dataverse trigger inconsistencies

(0) Share

Report

Posted on by Valentin99

Hi everyone,

I have two dataverse flows related to customer accounts in Dynamics 365 Finance & Operations:

One of the flows changes the "Account Status" and the "Account Status Reason" (which in turn changes the "Invoicing and delivery on hold" field).
The other flow is triggered when a row is modified. I have restricted the second flow so that it only triggers when these columns are changed:

However, for some tenants in D365, the first flow triggers the second flow. This shouldn't be the case, as none of the specified columns in the second flow's trigger are modified by the first flow. I don't know of any differences between tenants that could cause this problem. The customer dataverse table is a virtual table, if that's relevant.

Any ideas on the reason for this?