Unanswered

Failed to read metadata from file source. Response from the end service is : Bad Request

(0) Share

Report

Posted on by Community Power Pla...

Hello,

I'm trying to run a flow that grabs an excelreport template and a list of values from a seperate excel spreadsheet (SNAP Extract). Each line in the SNAP Extract spreadsheet contains all the data I need for a report.

The end goal is to go through and for each line in my SNAP extract create a report and save it as a new file.

This is currently working if I grab the files from OneDrive. The problem is that multiple people need to run this flow and if I share the OneDrive files with them they get a different path to the files. Flow cannot as I understand it access files that are shared with you.

My solution is to store the files on a share point site. Whenever anyone runs the flow I want them to essentially create an instance of the files. I do this by grabbing the file content from Sharepoint and creating a new file in excel and saving it into my onedrive.

This in itself works fine, I hit the ERROR when I try and handle the files I have just created.

The new file is created and it appears if I list the files in the folder but when try and use a 'get rows' node on it I get the error in the title.

I'm struggling to upload an Image of the error if I work it out I'll update this post.

Hope someone can help,

Thanks!

All responses (2)

Answers (0)

bouillons 302 on at

Like (0)

Report

Re: Failed to read metadata from file source. Response from the end service is : Bad Request

In my scenario I'm struggling with this as well. It only seems to work when I - the author of the flow - execute it. When another user triggers the flow, the file is created by the OneDrive for Business connector in THEIR OneDrive (as expected), but the Excel for Business connector gives an error when you attempt to perform actions on the file using the previously created file ID as input. It seems to look for the file in the flow author's OneDrive instead of the end user's OneDrive, at least that's my observation. I can create an "edit" share link in the same flow to the file, and this generates a web url that shows the file in the end user's OneDrive, so it's not an access permissions problem. In any case I see a difference in how the OneDrive for Business connector operates (executing in the scope of the end user) and the Excel for Business connector (executing in the scope of the author). I have an open support case with Microsoft to find out if it is a bug or by design, or if there's any workaround for having the Excel for Business connector operate in the scope of the end user.
v-xida-msft on at

Like (0)

Report
Re: Failed to read metadata from file source. Response from the end service is : Bad Request

Hi @Anonymous,

Could you please share a screenshot of your flow's configuration?

Further, could you please show a bit more about your error message?

I have made a test on my side and don't have the issue that you mentioned. My flow's configuration as below:

Grab the file content from SharePoint library and create a excel file in OneDriveThe flow works successfully as below:

Retrieve rows from the excel file
The flow works successfully as below:

Please check if you have created proper excel file in your OneDrive folder. In addition, please check if you have formatted the data of the excel file (original file) of your SharePoint library as a table, the Excel connector only connects to Tables currently.

More details about Excel connector, please check the following article:

https://docs.microsoft.com/en-us/connectors/excel/

Best regards,

Kris