Forum Discussion
Logic problem?
Hi Daz474,
Thank you for reaching out in Microsoft Community Forum.
Since the presence of a special character (like a smiley face) breaks the data load completely, the safest approach is to analyze the file in raw binary format before any parsing happens in Power BI.
Please follow these steps to safely identify the problematic row:
1.Use File.Contents to load the file as raw binary instead of as a table. This prevents Power BI from trying to parse corrupted characters.
2.Convert the binary into a list of lines using Lines.FromBinary.
3.Convert the list of lines into a table so you can inspect each one.
4.Add a column to flag lines that contain non-standard (non-ASCII) characters, such as emojis or symbols.
5.Optionally filter the table to only show the problematic rows, helping you isolate the account code.
Please continue using Microsoft Community Forum.
If this post helps in resolve your issue, kindly consider marking it as "Accept as Solution" and give it a 'Kudos' to help others find it more easily.
Regards,
Pavan.
Sorry for the delay!
This doesn't work because if the character is in the load then it won't load anything. I need to find the characters without loading it.
Hi Daz474,
Thank you for reaching out in Microsoft Community Forum.
Since the presence of a special character (like a smiley face) breaks the data load completely, the safest approach is to analyze the file in raw binary format before any parsing happens in Power BI.
Please follow these steps to safely identify the problematic row:
1.Use File.Contents to load the file as raw binary instead of as a table. This prevents Power BI from trying to parse corrupted characters.
2.Convert the binary into a list of lines using Lines.FromBinary.
3.Convert the list of lines into a table so you can inspect each one.
4.Add a column to flag lines that contain non-standard (non-ASCII) characters, such as emojis or symbols.
5.Optionally filter the table to only show the problematic rows, helping you isolate the account code.
Please continue using Microsoft Community Forum.
If this post helps in resolve your issue, kindly consider marking it as "Accept as Solution" and give it a 'Kudos' to help others find it more easily.
Regards,
Pavan.