I have a flow that is triggered when a SharePoint file is created. If the file is a log file it moves it to a sub folder but the issue is that when the file hits the sub folder the flow is triggered again and obviously fails since the source and destination is the same. Is there anything I can add to the flow to prevent it from looking in subfolders? I am trying to prevent moving the Logs folder out from within the main folder. Screenshot of the flow is below.
Accepted Solutions
Can you try using a different trigger: instead of when a file is created (properties only ) use When a file is created in a folder.
this allows you to pick any subfolder in your doc library and then move it to a different subfolder in the same library without "getting file properties.
In the condition use FileIdentifier ends with .log - see screen below.
hope this helps
Can you try using a different trigger: instead of when a file is created (properties only ) use When a file is created in a folder.
this allows you to pick any subfolder in your doc library and then move it to a different subfolder in the same library without "getting file properties.
In the condition use FileIdentifier ends with .log - see screen below.
hope this helps
Helpful resources
Welcome to the User Group Public Preview
Check out new user group experience and if you are a leader please create your group
Experience what’s next for Power Virtual Agents
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.
Power Platform ISV Studio
ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.
