I've created a flow which generates a PDF document and I'm using the Create File SharePoint connector.
If a file already exists in the SharePoint document library with the same file name as the one I'm trying to create, then Flow is returning an error as below.
I have made many flows like this in the past and I've never had this issue before.
Previously, when I have made flows like this, Flow would automatically create a new version of the file with the same file name and wouldn't return an error.
I don't understand why I could do this before, but now it's changed and I can't overwrite the file?
It's also worth noting that my flows I'd created previously are still working fine and overwriting the files as intended - it's just my new flow that I've made today that is returning the error. 🤔
Any help would be greatly appreciated!
Interesting scenario, I will try to reproduce the same when once I have a spare time and let you know the outcome.
If I find info about it I will also let you know.
I'm experiencing the same issue. For the option "If a file already exists", I tried both "Replace" and "Copy with a new name":
The action still returns a "file already exists" error.
Hi all, I managed to to temporarily get past this by doing the following:
The images below should explain in further detail:
I found a solution to this that means you don't have to put in conditions\scopes on whether the file is already there
Not sure if this a recommended long term best practice, but it works.
I also had old flows that did overwrite the file in SharePoint, but as above new 'Create file' does not allow it.
So I looked at one of the Microsoft Automate templates 'Copy new files from PC to SharePoint'
I copied to clipboard the 'Create file' action from that template into the flow I was having problems with, cleared existing fields in it action and replaced them with my own and it worked, it overwrote the files.
I suspect you could also copy from an old flow that worked in the same way.
So from this I gather when Microsoft make changes to these actions they make it so it only applies if you are adding the 'action' from new. So if it worked on an older flow, then copy that action from the older flow and you should have the old situation.
Not sure if this issue is a bug on new action or intentional from Microsoft.
Give a thumbs up if this works for you, as it cost me a lot of time trying to get a workaround in place when the solution , in the end , was very simple and hidden in plain sight!
Check out the on demand sessions that are available now!
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.