Unanswered

Changing name is not supported for this scenario - Onedrive

(0) Share

Report

Posted on by Bubblebeb

I have a flow that every night copies a file (using the OneDrive Copy File Action) from my Onedrive folder and writes it to another folder in Onedrive. When copying it it also renames the file using the expression below.

concat('/Documents/Project/Backups/',utcNow('yyMMdd'),' ','Report.xlsx')

Today it has failed with the error message below.

{

"status": 400,

"message": "Changing name is not supported for this scenario",

"source": "api.connectorp.svc.ms"

}

Any ideas why this is now not supported and how I can resolve it?

Categories:

Using flows

I have the same question (0)

All responses (6)

Answers (0)

ChadC1 6 on at

Like (0)

Report

I'm also having a similar issue with my flow that started today. It copies a file weekly, and ran fine last week, but erroring out today. No changes have happened within the flow to break this. Have exact error message:

{
  "status": 400,
  "message": "Changing name is not supported for this scenario",
  "source": "api.connectorp.svc.ms"
}

Was this reply helpful? Yes No
Rohit Sharma354 on at

Like (0)

Report

Hello,

Please try renaming the file using below connector action and see if this helps resolving the error:

https://docs.microsoft.com/en-us/connectors/onedrive/#move-or-rename-a-file

https://docs.microsoft.com/en-us/connectors/onedrive/#move-or-rename-a-file

Was this reply helpful? Yes No
Bubblebeb 6 on at

Like (0)

Report

I did try this one but it moves and renames.
I need the file to remain where it is and a copy be placed in a backup folder with the new name.

I tried using the Copy connector to copy the file first them the move or rename connector to rename it but it doesn't copy the file fast enough for the renaming to happen. It just fails stating that the file was not in the location for renaming.

Was this reply helpful? Yes No
ChadC1 6 on at

Like (1)

Report
I was able to get my flow working again by doing the following. Seems like more steps to accomplish what was 1 simple step last week using the copy file step.

The goal of my flow was to copy a master file and put it in the current location with the date on it, and keep the original file. So at the end of the flow, I have FILE_Original.docx, and FILE_Original_06262020.docx.

Setup a step using 'Copy file using path' that copied the file from /PATH/DOC.docx to /Path/Temp/Doc.docx
Setup a step using 'Move or rename a file using path' to move /PATH/Temp/doc.docx to /Path/Doc_06262020.docx
So basically, copy the file somewhere else, then move it back with the correct name.

Was this reply helpful? Yes No
Bubblebeb 6 on at

Like (0)

Report

I have found that the time it takes to copy the file the rename connector failed as it didn't see the file in the destination folder in time.
I have now had to have 2 flows which run 5 mins apart. One to copy the file then another to rename.

Very frustrating for MS to change the copy functionality.

Was this reply helpful? Yes No
Bubblebeb 6 on at

Like (0)

Report

Looks like Microsoft have reinstated the reman function in the copy connector.
After a week of trying to resolve it I tried my original again and it works.

Problem solved. (Hopefully)

Was this reply helpful? Yes No