I have created a Flow that occurs when a new Channel is created within Teams. Since that creates a folder within the related Documents Library in SharePoint, I have it automatically creating additional Folders within that created "Channel Folder".
I have it set so that the when the Correspondence folder is created, it doesn't trigger the Flow again. However, if someone adds a folder within one of these folders, the Flow triggers again.
How can I make sure that this flow will only happen when it's on the Root, but also provide the flexibility if a folder is needed within one of these folders?
Solved! Go to Solution.
Haveyou considered using trigger conditions?
Or would you prefer to use conditions.
I woudl probably have a look at the output from the trigger and check if you have the url of the folder that is created anywhere. Then split that by '/' and count the number of elements. this should then help you configure the condition to identify if you have a folder/channel or a subfolder
Haveyou considered using trigger conditions?
Or would you prefer to use conditions.
I woudl probably have a look at the output from the trigger and check if you have the url of the folder that is created anywhere. Then split that by '/' and count the number of elements. this should then help you configure the condition to identify if you have a folder/channel or a subfolder
I was so close, but I had some blinders on. While I had used conditions to make sure that if the folder did not match one of the names of the folders, I didn't think to use the conditions to have it look at the Folder Path and have it end with "Shared Documents/"
While it will still triggers the workflow if you are right in Shared Documents - the main goal is to make sure it doesn't trigger within the folders - and for what we need, most often the end users would not be in the root of Shared Documents.
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!
User | Count |
---|---|
41 | |
40 | |
37 | |
32 | |
31 |
User | Count |
---|---|
52 | |
39 | |
35 | |
33 | |
24 |