Flow/SharePoint - File Already Exists?

[hiccup]

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!

[danielbazetto]

Hi @hiccup 

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.

[thomas_schick]

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.

[danielbazetto]

Hi @hiccup and @thomas_schick 

I might have missed the last entry on the thread, are you guys still facing the same issue?

[Anonymous]

I'm facing the same issue.

[Anonymous]

I am facing the same issue. Throws file already exists error for new flows, but old ones still works. Please let me know if this has been changed.

Thanks,

Nowshad

[bkeano]

Hi

I have the same issue, previous flows overwrite, but new flows give the error.

The SharePoint library settings have not changed, version control is on etc

[NeohLooi]

Same situation on here too. I was very frustrated on this scenario, hope Microsoft have a way to solve this issue as soon as possible.

[hiccup]

Hi all, I managed to to temporarily get past this by doing the following:

• Add a parallel branch after the 'Create File' step. One branch will run if Create File runs successfully (i.e. a new file is created) and the second branch will run if it has failed (i.e. getting file already exists error).
• In the parallel branch add a 'Get Files (properties only)' step, connect to your SharePoint site and add a Filter query to retrieve the file you're trying to amend.
• Change the 'configure run after' on the 'Get Files' step to 'On Failed'.
• Then add an 'Update File' step underneath and put the contents of the file into there (this will likely auto-update to an Apply to Each but that's fine since I'm only ever retrieving 1 file).

The images below should explain in further detail:

[bkeano · Accepted solution]

Hi

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!

[Anonymous]

Hello,

You can  replace ‘Create file ’ with 'Update File'. Thanks!

[virakones]

Hi @danielbazetto 

Is there an update available? Is the "Create File" Sharepoint action able to overwrite already existing files?

[Psawyer2]

Any Update

[takolota]

I resolved a similar issue but where I didn’t want to loose the old file.

Before creating the new file, I used the Get files (properties only) to retrieve every file from the folder I’m about to create a file in. (Had to increase pagination thresholds to get it to pick up my file though).

Then below that I used a conditional to check any files properties returned with file name with extension that equals the file name I’m about to use.

If true, then I Get file content, Create a new file in the folder with the file content and a combination of the file name and a utcnow() time stamp. Then I delete the original file currently occupying the name I need.

that way I have a copy of the old file with a time-stamp to archive away and the most recent file using the standardized name so I can easily reference it in later flows.

it also avoids some potential issues with parallel branches and failed steps where you can’t reference dynamic content from failed create file steps.

 

[Anonymous]

I know this is an old post but if you go to create file settings and disable "allow chunking" it will fix this issue

[peoute_bju]

Thanks! This seemed to fix it for me, too.

[Karthik-S-SBA]

Hi,

I faced the same issue, while implementing one of the solutions from this thread, I realized a simpler solution.

Add a delete file before the create file.
and make the create file "run after" to both success and failure.

[SharonFryLV]

This solution from freeluv to disable "Allow chunking" worked for me! File gets replaced with a new version - exactly what I wanted/expected. Thanks @Anonymous!

For those who may be unclear, here are screenshots of the steps:

In the bottom of the Settings window for the Step:

[debosmita03]

 Disabling "Allow chunking" worked for me!

[djbryson]

Deleting the file first would only be an option if you didn't care about versions.  You're also changing the default behavior.  If you drag a file into a folder, and the file already exists, it will replace and create a new version.  Your Power Automate Flow should replicate default behavior.