Renaming files in SharePoint using the name of a file already existing in the library

(0) Share

Report

Posted on by Gilmour

362

The process I'm trying to build is:

1. upload a file to a SharePoint library

2. rename the new file using the name of an existing file, so the old file is kept as a version.

SharePoint just won't rename the new file, since the name is used for an existing file.

Is there a setting in SharePoint I need to change to allow files to be renamed with the name of an existing file, or is there a way to do it using PowerApps and Power Automate?

I know that I could simply rename the new file and THEN upload it to SharePoint, but it won't work with the solution I am trying to build.

Thanks to whomever can help!

Categories:

Building Power Apps

I have the same question (0)

All responses (13)

Answers (0)

Sort by

subsguts 1,259 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

I found the following command at the link below. So not my idea, but it appears this will solve you problem?
Power Automate Rename File - EnjoySharePoint

Was this reply helpful? Yes No
Pstork1 69,577 Most Valuable Professional on at

Like
a
(2)

Report
Copy link

Link copied!

You can't rename a new file to be the same as an existing filename. Even if you could it would overwrite the existing file, not save it as a new version. This blog shows you how it can be accomplished.

How to update (not replace) an existing file in Power Automate (tomriha.com)

Was this reply helpful? Yes No
Gilmour 362 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Pstork1, thank you for taking the time.

I am getting the following error:

Missing or mismatched field definition on the destination list for source field '_ExtendedDescription' type 'Note'. Source site template id 'GroupWebTemplateID', target site template id 'GroupWebTemplateID'. Total blocked root objects in this operation is [1].
clientRequestId: etc...

The only thing I've done differently is using a source and destination libraries in the same site. Does the solution require that the libraries are actually in two different sites? Below are screenshots of my flow.

The first action of the flow (PowerApps) provides the file path and name for the two files using inputs OldFilePathname and NewFilePathName. The flow output for the actions seems to be correct.

Thank you for helping!

Was this reply helpful? Yes No
Gilmour 362 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @subsguts. I’m going to give the solution suggested by PStork1 a try, as it seems simpler. Thank you for taking the time!

Was this reply helpful? Yes No
Pstork1 69,577 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Take another look at the article. Its supposed to fail. Then you set the run after setting on the get file properties to run only if the previous action fails. Based on your screenshot you didn't do that.

Was this reply helpful? Yes No
Gilmour 362 on at

Like
a
(0)

Report
Copy link

Link copied!

I tried to rebuild the flow per screenshots below, but now I am getting a new error message:

Missing or mismatched field definition on the destination list for source field '_ExtendedDescription' type 'Note'. Source site template id 'GroupWebTemplateID', target site template id 'GroupWebTemplateID'. Total blocked root objects in this operation is [1].

What am I doing wrong?

Thank you for your help!

Was this reply helpful? Yes No
Pstork1 69,577 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

The library you are copying the file to seems to have an additional metadata field of type 'Note' in it. That seems to have been set as a required field and needs to be updated when the file is copied. I'm not sure how you would do that using this method. I think that the existence of that field is going to keep you from being able to add a file as a new version.

Was this reply helpful? Yes No
Gilmour 362 on at

Like
a
(0)

Report
Copy link

Link copied!

Nope, no trace of such field.
Except for (file) Name, the library has no required fields (all the metadata is provisioned via PowerApps).
Could it be a field once existing and then removed? I doubt it, but it's the only other thing I can try. If so, I wouldn't know where to look for "ghost" fields...
What a headache!

Was this reply helpful? Yes No
Pstork1 69,577 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Not sure what else to suggest. It could be a field that was later deleted. You might try just creating two new document libraries and see if you can get the concept to work.

Was this reply helpful? Yes No
subsguts 1,259 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

Considering your struggles, I would think knowing more about why the following is not possible would be useful:

"I know that I could simply rename the new file and THEN upload it to SharePoint, but it won't work with the solution I am trying to build."

I only mention it because often when I'm trying to force a solution that I have in my mind maybe there is a different method to reach the same objective. From an outsider's perspective it seems like you are going out of your way to create a version of a document, which is functionality SharePoint already provides if you simply upload a new version. So, I'm just wondering why this is a requirement is all.

Maybe if that requirement is known to myself and others can get you to what you need without this complexity. Just a suggestion...

Was this reply helpful? Yes No