Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

exporting PowerBI tables as CSVs produce UTF-8 with BOM (remove the BOM!) #222

Closed
dan-reznik opened this issue Sep 27, 2019 · 1 comment
Closed
Assignees

Comments

@dan-reznik
Copy link

@dan-reznik dan-reznik commented Sep 27, 2019

When using DaxStudio to export a whole PBI table as a CSV, the exported file is a UTF-8 (good) but with a BOM (not necessary)

The UTF-8 BOM is a sequence of Bytes at the start of a text-stream (EF BB BF) that allows the reader to more reliably guess a file as being encoded in UTF-8. Normally, the BOM is used to signal the endianness of an encoding, but since endianness is irrelevant to UTF-8, the BOM is unnecessary.

@dgosbell dgosbell self-assigned this Sep 27, 2019
@dgosbell dgosbell added the bug label Sep 27, 2019
@dgosbell

This comment has been minimized.

Copy link
Contributor

@dgosbell dgosbell commented Sep 27, 2019

Thanks for pointing this out. It turns out that historically Microsoft chose to include the BOM with UTF8 back in the early 2000's so they left this as the default option so as not to break existing code. I've switched this option off now and the fix will be in the next release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.