Solved: Bad Request Error

newautomater · ‎07-05-2021

Happy 4th of July!

Building a flow that attempts to grab a sharepoint list weekly, convert it to a .xls file, and then email that file every Monday. I am getting the below error at the "Create file" stage. I have posted the flow below the error. Any assistance would be great

Bad Request - <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Bad Request - Invalid URL</h2>
<hr><p>HTTP Error 400. The request URL is invalid.</p>
</BODY></HTML>

tom_riha · ‎07-05-2021

Hello @newautomater ,

I’m not sure if you can create an .xls file as that’s a complicated file type, and also if you can use the html table as a source.
I’d create a .csv file instead, using the ‘Create csv table’ instead of the creation of an html table.

[ If I have answered your question, please Accept the post as a solution. ]
[ If you like my response, please give it a Thumbs Up. ]

[ I also blog about Power Automate solutions even for non-IT people. ]

View solution in original post

tom_riha · ‎07-05-2021

Hello @newautomater ,

I’m not sure if you can create an .xls file as that’s a complicated file type, and also if you can use the html table as a source.
I’d create a .csv file instead, using the ‘Create csv table’ instead of the creation of an html table.

[ If I have answered your question, please Accept the post as a solution. ]
[ If you like my response, please give it a Thumbs Up. ]

[ I also blog about Power Automate solutions even for non-IT people. ]

newautomater · ‎07-05-2021

Hi there,

This was a good idea. I changed the Output.xls step to CSV. I left content as just file content and switched to a non-dynamic name instead of the output.xls, which didn't make a bunch of sense to me when thinking about it since the output would be an entire list. This worked for me! I've done an .xls before from html and I think some of these steps weren't exactly needed. However, this workaround came through!

Bad Request Error

Helpful resources

Power Automate News & Announcements

Power Automate Community Blog

Help make Flow Design easier