I have a simple flow that checks if the billing id is empty or not after the form has been modified.
IF Empty - no action is taken
IF NOT - email is sent - update item
The item is being updated, however the email is being sent infinitely. I tried to use the Terminate control but it didnt help.
I need assistance on how to approach this please
This is because the "update item" action in the flow would update the item, and as soon as the item is updated, the flow would be triggered again.
Please take a try to add a Yes/No type column "UpdateByFlow" in the sharepoint list.and set the defaults value of the "UpdateByFlow" to "No". Also please make sure when an item is modified manually in the sharepoint list,the "UpdateByFlow" column is setted to "No"
Then you could add a condition under the trigger to check if the "UpdateByFlow" column is equal to "true",if the UpdateByFlow" column is equal to "False",inside the If no branch of the condition,add a Condition to check if the billing id is empty or not.
And please make sure the "UpdateByFlow" column in the "Update item" action in the flow would be set to "Yes".
I tried this as a solution and I'm still getting infinite emails
First, I created an "UpdateByFlow" column on my SharePoint list with a yes/no choice and used no as default.
Here's the flow:
What am I doing wrong here? Can you simulate this problem and show me a screenshot?
This to me is a major gap that needs to be closed by Flow itself.
There needs to be some kind of way to update an item WITHOUT triggering a subsequent flow. SharePoint Designer could do it. Other products can do it. Using "elevated" rights would do it.
I have Flow after Flow that use like 6 runs when it only technically needs to do 1. Then the users have to come up with crazy if and terminate statements to try and keep this from happening. Where Flow is becoming a Pay-model, this is pretty ridiculous, and I'd expect the Flow limits to ultimately increase for the amount of unintended Flows that are triggered.
Ideally, I'm thinking some kind of trigger option (like where the new View option is) that allows you to set criteria by which the Flow should NOT trigger (e.g. if updated by this user, if this field is set, etc), and hence not count against your quota.
Read the announcement for more information!
Congrats to the finalists of our ‘Better Together’-themed T-shirt design contest! Click for the top entries.
We've updated and improved the layout and uploading format of the Power Automate Cookbook!
Fill out a quick form to claim your user group badge now!
The top training and networking event across the globe for Microsoft Business Applications