Hello community,
I have a flow in a Sharepoint List that is triggered by "When an item is modified" however I need it NOT TO RUN when another flow modified that item. I need it to run only when humans did any change.
I tried some Trigger Conditions, but I failed horribly.
Thanks!
Yes I'm trying to prevent infinite loops.
There is 1 main list with groups of columns A, B, and C; and 3 other lists with different permission access (3 diff teams) with the same group of columns A (list a), B (list b), and C (list c). So, each of those 3 other lists feeds the Main list.
However, the main list is handled by a team with access to all 3 areas (A, B, and C) so any changes made directly to the Main List should update the other 3 lists as well.
I mentioned it because it is possible. But I do not recommend it at all. It will lead to other problems.
It is basically an attempt to band-aid patch something that is under developed. It would only work effectively if you were entirely in control of the flows, list, and data. That way when something goes wrong, you know why and how to fix it.
If you share your flow and more about what specifically you would like to accomplish with triggers or changes, it would be easier to develop a potential solution.
What does your initial flow do? What changes to columns would people manually make? What does your secondary flow do?
Are you trying to prevent an infinite loop?
Thanks for helping.
If the flow was created by me, doesn't it indicates my authorship somehow? Reason I'm asking is because I'm not gonna be using this List I made it for other people, so if by excluding me with an "@not" solves the thing, I'm ok with it.
You won't be able to have a simple trigger based on if a flow making the changes vs a person.
(There is a way which is not good, not recommended, but works in very specific situations. It would be based on Modified By, so like if your flow is making the changes, your name goes into the Modified By. So then if someone else manually makes a change, the flow is triggered and checks the Modified By column to see if it was your name or different. Of course this doesn't work if flows are shared or you are the one manually changing items.)
You will have to set up your list and your flow logic to do what you want. That may include putting some kind of signal/status column(s) that you can use to check. Like the other flow makes a change in that status column and then when the new flow is triggered it checks the column. (Of course now you have to manage the new status column and when it is changed.)
Or you could see if there is a way to combine your other flow and the new flow to work together within the same flow. So you could delete the separate flows and just have a single larger flow.
That is the hard part and creative part of designing flow processes.