This is meant to be a work-around for the Row Filter in automated flows. The issue is being tracked by Microsoft as a bug - but regardless...
It has been sometime now that filtering rows in Power Automate in order to more efficiently control the API calls and optimize the flow triggers is not working as expected.
For a single/simple filter like this (below), things may seem promising, but after transferring the flow over to another environment things start to break down.
For a slightly more complex filter like the one below (nothing too fancy), you might notice right away that your trigger is not working - Always check the Flow Checker.
As a work-around, you can set up a trigger condition using an expression which will essentially do the same thing as the row filter. To achieve that, click on the ellipses on the top right of your trigger (1), and then go to Settings (2).
To mimic my simple and simple+ row filters, I used the equals function the same way you would inside the flow for any other reason. To add another parameter to my condition, I used the AND statement/function - you can use OR in the same way.
Have a look at the Power Automate and Azure Logic Apps functions here.
Prefix you condition with the @ symbol as this is how Power Automate will read it, and you are ready to give it a try.
Note that if you are testing your flow with previous tests or runs, you will get an error:
Try triggering a new flow the same way your trigger expects it, and you should be OK.
Comments