I would have a question, please refer to the step #3 in my flow design below.
I am building a flow which would extract SP list attachement(s) and copies them into a general folder. A 2nd flow should move files from a general library into specific folders based on file names.
I am not sure whether the 3rd step is technically buildable.
Thank you for comments.
Solved! Go to Solution.
Hi @abm ,
Thank you very much for this design.
I was wondering whether a 'folder existence check' condition can be added into your flow in order to determine the folder with the name already exists or not in the library (it can happen that the same person submits more app records which would cause folder name duplicates or flow fail).
Something like after 'Compose' action where we extracted the folder name to put a condition for folder existence check based on the name. If the folder exists -> do a Move file into it, if not perform the Create new folder and move file into it.
Thank you for suggestions.
Thanks for your reply.
You can use the create folder action step without checking whether folder exists or not. If folder already exists it won't recreate the folder. If you want explicitly check then please see my blog link below.
Hi @abm ,
Thank you for your explanation and help on this design.
Am I right in my understanding of your comment that if the folder already exists the action step 'Create a folder' will not create a duplicated folder and the action step 'Create a folder' will be passed as successful without any action done and the file will be moved in the subsequent action step into it.
And this way the initially created folder will absorb new and new attachments if the same person submits the app again (the folder to be named always as the appsubmitter).
Thank you once again.
Check out new user group experience and if you are a leader please create your group
May the fourth be with you, join us online!
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.
ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.