Forum Discussion
Xml processing failed. Internal error: '\b', hexadecimal value 0x08, is an invalid character.
I'm posting a solution I found here in case anyone runs into the same problem. The beauty of this is that you can do it without much programming knowledge like I am.
What worked for me is to use Power Automate to get xml file, look into its content, strip the invalid characters before saving the file to SharePoint. After that, I only need to establish data connection between Power BI and the sanitised xml file on SharePoint.
The solution can be found here. It belongs to AlanPs1 and all credits should be given to him for a very neat solution.
Super User(1) Familiarise yourself with the " try ... otherwise ... " concept in Power Query.
Thank you for your input
From what I know, Power Query refuses to parse the xml file in the first place. If data could be read, even with error records, I would have simply deleted the entire "email content" column containing the invalid characters because only request counts is needed and other columns can be used. Unfortunately no matter what I tried, I'm always stuck at the very first step.
As I mentioned in the original post, by default the RSS link will always contain the content of the first email sent to us.
Since I'm not a developer and I'm very new to Power BI, I may have misunderstood your point. Could you please be more specific?
- lbendlin
Post a sanitized version of your Power Query code and I will show you how to include the error handling.
let Source = Xml.Tables(Web.Contents("https://................../?Order=ASC%7CASC%7CASC%7CASC&OrderBy=id%7C%7C%7C&Query=Queue+%3D+%27Property%27+AND+Created+%3E+%2712+DAYS+AGO%27")), ...... in #"Filtered Rows"I don't know programming so what you see above is entirely generated by Power Query. There are other lines but I didn't include them as they are just commands to expand tables, remove, filter, etc.