Check this out !!!
Trigger Conditions - we can now specify the trigger condition for the Flow - save Flow runs 🙂
Condition based Flow Triggers 🙂
My Vlog on Flow Trigger Conditions - https://powerusers.microsoft.com/t5/Webinars-and-Video-Gallery/Microsoft-Flow-Trigger-Conditions/m-p...
Solved! Go to Solution.
ok, think I've got it, the format needed to be:
@equals(triggerBody()?.Status, 'Pending Project Manager Approval')
It at least saved with that format, now for testing...
Hi @RezaDorrani ,
Thank you for your sharing, the Trigger conditions for Flow is very useful and we would benifit from it.
Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks Reza!!! It took a little tweaking to get it to work for different types of fields, but your video walked me through it and I was not only able to make it work for my application. Not only that, I found that I could enclose the equals string inside a Not() to get the inverse effect, where every condition of a choice field would run the workflow except one, which was the default setting at the end of the workflow. In my application, the user has to select a choice in the editing of the list item, which invoked a switch case in the workflow. I reset it to the default state when I make my field updates. Using this process and your tip on adding a trigger condition, I have now made my workflow only run once. Thanks again! This will be very useful going forward.
Explore the latest innovations, learn from product experts and partners, level up your skillset, and create connections from around the world.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.