Answered

Dataverse 'Apply to Each' is updating more records than expected

(0) Share

Report

Posted on by 404 Not Found

I am new to Power Automate and I am trying to understand what I am doing wrong with this flow.

I have a list from Dataverse, I am applying a Filter array that is removing records that have a status of 'Closed' (custom field). I can see in the INPUTS that there is a record with a status of 'Closed'... this record is correctly filtered and is not in the OUTPUT.

The OUTPUT contains 7 records, however the 'Apply to Each' is receiving 8 records, including the one that was filtered out in the prior step.

I am not sure what I am missing here.

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (2)

Sort by

shaboo 65 on at

Like (0)

Report
Copy link

Link copied!

Hiya,

Can you create same filter on a view and see how many records you are retrieving, it will be the same filter it uses on flow. Download and view XML and compare the power automate filter.

If there will be issue what you see from view and power automate the number of records resulting different when if the filter is same that will be a bug on Microsoft end that is unlikely happen.

Hope this is helpful.

Regards
Sandeep

Was this reply helpful? Yes No
404 Not Found 11 on at

Like (0)

Report
Copy link

Link copied!

Thanks for your reply... as I continue to dig I think my issue is somewhere in the Apply to Each... I can see that when I pick the value, it is referring to the original list, and not the output from the filter...

But if I try to pick one of the options under the filter it errors out as the step is receiving an object and not the array. I think I am missing some sort of intermediary step...

Ugh, this would be like a 15 minute stored procedure...

Was this reply helpful? Yes No
Verified answer

v-dezhili-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @vtchris

Please try:

or

Best Regards,
Dezhi

Was this reply helpful? Yes No
Verified answer

404 Not Found 11 on at

Like (0)

Report
Copy link

Link copied!

Thanks for your reply!

I did try your first example previously... this errored out when I tried to update the row because the step was receiving an object and not an array.

For the second example, I am using the filter rows in the 'List Rows' to remove records with nulls which reduces the most records. Unfortunately I was not able to find a way to apply multiple filters at this stage, and so I ended up with the 'Filter array' step.

Ultimately I solved it by using a Condition and only update the records that don't contain 'Closed' in the status. It seems silly to have to go through each record, but I did not discover a way to implement the 'Filter array' WITH the 'Update row'. Now I need to look into paging as either way this is going to get more than 5,000 records when it is in the prod environment.

I appreciate the dialogue on this issue from the community! I wish I could have found a more efficient solution.

Was this reply helpful? Yes No