D365FO - Filter rows in dataverse trigger (Power Automate)

(2) Share

Report

Posted on by Adis

6,226 Super User 2026 Season 1

Dear all,

I started using the dataverse connector instead the Fin&Ops connector.

I wanted to know if I messed up something here or if it just works like this.

I tested this flow and works on generally fine. However, the delete action works differently then the modified and add action.

So, when I add a new line in D365FO or modify an existing one, it works according to the Filter rows condition.

However, when I delete a row, it should NOT run the flow if the mserp_resourceid is not empty, but it does.

Did you encounter a similar behaviour where the delete action, does not behave according to the Filter rows?

Thanks in advance, Adis

Categories:

Power Platform integration

I have the same question (0)

All responses (5)

Answers (1)

Jonas "Jones&q... 5,006 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Don't recall us having any issues, so I wonder if it's related to F&O. Need to have a play...

I like to use trigger conditions as it gives me more control of when a flow get's triggered, and it should also reduce flow runs. Give it a try and see if it's more consistent.

https://learn.microsoft.com/en-us/power-automate/triggers-introduction?tabs=new-designer#use-trigger-conditions-to-reduce-flow-runs
https://citizendevelopmentacademy.com/blog/power-automate-trigger-conditions/

Was this reply helpful? Yes No
Verified answer

Jonas "Jones&q... 5,006 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Yep, looks to be a limitation in the filter row parameter on virtual entities. I managed to reproduce it in my playground using a standard entity.

If I instead specify a trigger condition, it's not triggering on deletes.

Was this reply helpful? Yes No
Adis 6,226 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Thanks Jonas 💪

I do use the trigger conditions to reduce the flow runs, however, I noticed that using the filters rows, the flow isnt triggered at all if the conidition isnt met.

So I thought, lets give it a try as it is more visible if there are any trigger conditions.

I ll get back to the triggers 😊

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 302,629 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Adis,

The first field on the action is called Change type. You can change this to Added or Modified. It will then skip the delete actions. Your current setting includes the deletes.

Was this reply helpful? Yes No
Adis 6,226 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi André,

By reading my question I understand that its a bit confusing. Yes, I noticed the change type field.

I want to trigger the flow also on delete actions, however, adding and modifying works according the filter rows, where delete action did not respect the conditions in filter rows field.

It ignored the condition in filter row mserp_resourceid eq '' and contains(mserp_categoryid ,'INORM') - so even the mserp_resourceID was NOT empty it was triggered on delete action.

But with the answer of Jonas, I switched to trigger conditions and it worked.

my trigger condition:

@OR

(contains(triggerBody()?['mserp_categoryid'],'OH'),

AND

(equals(triggerBody()?['mserp_resourceid'],''),

contains(triggerBody()?['mserp_categoryid'],'INORM')))

side Note:

I was copying the trigger condition from another flow with a business event connector from FinOps and had some issues at it didnt work with the dataverse connector, because the there is a difference in the syntax of the trigger condition

with FinOps connector the trigger condition would be:

@equals(triggerBody()?['body/mserp_resourceid'],'')

with dataverse connector the trigger condition would be:

@equals(triggerBody()?['mserp_resourceid'],'')

So the part "body/" needs to be deleted. Maybe its obv for developers, but for me it wasnt.

Kind regards, Adis

Was this reply helpful? Yes No