Unanswered

One Drive File ID has changed.

(3) Share

Report

Posted on by vz333

I have a couple of automations that grab files out of OneDrive when they are created and move them to sharepoint. The flows have been working just fine for a few years. Suddenly they are not.

I am getting this error trying to access the contents of the file after getting the file properties of the file:

{
"status": 400,
"message": "The file id '0123456789ABCDEF!s0123456789abcdef0123456789abcdef' is not valid.",
"source": "api.connectorp.svc.ms"
}

So going back to the runs that worked it seems that every One Drive file had an ID like this:

0123456789ABCDEF!01234

where the part after the ! is unique. The part before I assume represents my account.

From the runs that fail, the ID looks like this:

0123456789ABCDEF!s0123456789abcdef0123456789abcdef

Where again, the part before the ! looks like my account and the part after looks like the unique file id. But the service, api.connectorp.svc.ms does not accept it.

The FileLocator is identical to the Id and there is nothing else that looks like an Id I could use.

So, what do I do to fix this?

Categories:

General topics

I have the same question (0)

All responses (16)

Answers (0)

SudeepGhatakNZ 14,394 Most Valuable Professional on at

Like (0)

Report

Can you please post a screenshot of your flow in design mode?

Was this reply helpful? Yes No
vz333 14 on at

Like (0)

Report

Nothing special. Gets a file in step 1, supposed to get the contents in step 2 but fails now.

Was this reply helpful? Yes No
SudeepGhatakNZ 14,394 Most Valuable Professional on at

Like (0)

Report

On surface your flow looks okay but maybe the reference Ids could have changed.

There is a template you can use

Move file from OneDrive for Business to SharePoint and notify me | Microsoft Power Automate

Was this reply helpful? Yes No
vz333 14 on at

Like (1)

Report

This works better as it avoids the two steps I took before to get file contents to create the sharepoint file. I am not sure why I had two steps before, but it was working for years so there was no reason to visit it until now.
However, even though the file id was not needed to create the sharepoint file now, it is used in the above template to delete the OneDrive file afterwards. And it still does not like the new file id.

So, this gets me closer to what I need. But there is an underlying problem with OneDrive's new file id length, I feel, as the api call used to manipulate the file does no like it.

Was this reply helpful? Yes No
SudeepGhatakNZ 14,394 Most Valuable Professional on at

Like (0)

Report

Are you sure you are specifying the File Identifier field and not the Id field?

Was this reply helpful? Yes No
vz333 14 on at

Like (0)

Report

Of course.

Was this reply helpful? Yes No
SudeepGhatakNZ 14,394 Most Valuable Professional on at

Like (0)

Report

Just tested successfully at my end. I am out of ideas atm.

Was this reply helpful? Yes No
vz333 14 on at

Like (0)

Report

Your file ID is much different than mine. Also, I did not use OneDrive for business. I am using OneDrive Personal as this an at home project. That may be where the difference lies.

Was this reply helpful? Yes No
vz333 14 on at

Like (0)

Report

Thanks for your help. For now, at least, I have replaced OneDrive with an alternative option and all is good with the flow.

Was this reply helpful? Yes No
dev@iwasaki 3 on at

Like (0)

Report

Were you able to resolve this issue? The exact same thing is happening again after the Microsoft-Crowdstrike outage. It seems that only newly created files in OneDrive are affected (proven after multiple testing).

I'd appreciate it if anyone can provide any solutions on this. THANK YOUUUU!

Was this reply helpful? Yes No