I've a regular running flow that has to update a text file on my public account's OneDrive (so not for OD for Business). The filename depends on a date, and is not fixed. Until and including March 29th 2025 updating this file was working just fine; it used a file id with a 6 digit number behind the ! in the found file id (e.g. ). As of March 30th 2025 the file ID part following the ! suddenly changed to a string with33 characters (starting with a 's' followed with an guid like number without the '-', e.g. ), and with this the Update file action started to fail.
If I use the folder name and the filename from a compose as the file path in the ID field, the action also fails. Does anyone experiences this as well, and is there a way to resolve this???
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
9
Share
Report
All responses (
Answers (
