cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Advocate I
Advocate I

Overwrite file when creating a file in SharePoint

Hey guys,

in the recent flows I created it was normal that an existing file in SharePoint was simply overwritten when it had the same name as the new file. 
Right now I am creating a flow and Automate doesn't behave like this anymore, whenever I try to create a file with the same name I get an error.
Any solutions for that?

Thanks, Julian

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Resolver I
Resolver I

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!

BTW: Versioning is turned on in my site, so solution is not there

 

View solution in original post

11 REPLIES 11
Highlighted
New Member

I am experiencing the same issue....very strange

Highlighted
Resident Rockstar
Resident Rockstar

@nbot 

I have recently experienced the same issue in flow but i believe it is much related to sharepoint versioning rather than flow.

If this post helps you with your problem, please mark your as Accepted solution.If you like my response, please give it a Thumbs Up.
Highlighted

Did you find any solution for that? The weird things is that it only occurs at "new flows", my old ones still function normally... 

Highlighted
New Member

I'm having same issue.  My new flow will not overwrite the csv file but yet another older flow that I created a few months ago is able to overwrite its file.

Highlighted
Frequent Visitor

Try to use the "Update File" action if the file exists.

Highlighted

Whats the best way to check if file exists?

Highlighted
Resolver I
Resolver I

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!

BTW: Versioning is turned on in my site, so solution is not there

 

View solution in original post

Highlighted
New Member

Turning "Allow chunking" OFF in the Create File settings worked for me. 

EnriqueC_0-1602018799274.png

 

Highlighted

Does this do anything else? 

It is mentioning "HTTP",  does this imply that data is transferred to SP over HTTP? 

Highlighted
New Member

@bkeano can you look at the code behind the action that works and share the results here?  You can use the Peek Code option from the menu on the action to compare what it is doing, it's possible there is some other parameter being included.  I am having the same issue but don't have an action that works to copy.  thank you

Highlighted

@AK3800 , please see below, I replaced our tenant name and site name, but the rest is the peek code from the create SP file
{
"inputs": {
"host": {
"connection": {
"name": "@parameters('$connections')['shared_sharepointonline_1']['connectionId']"
}
},
"method": "post",
"body": "@body('Get_file_content_using_path')",
"path": "/datasets/@{encodeURIComponent(encodeURIComponent('https://TENNANT.sharepoint.com/sites/OURSite'))}/files",
"queries": {
"folderPath": "/Shared Documents",
"name": "@triggerBody()?['Name']"
},
"authentication": "@parameters('$authentication')"
},
"metadata": {
"flowSystemMetadata": {
"swaggerOperationId": "CreateFile"
}
}
}

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

Power Platform ISV Studio

Power Platform ISV Studio

ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.

Top Kudoed Authors
Users online (12,175)