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

Weird Character in Field Titles - Excel Export #308

Closed
BlierM opened this issue Apr 8, 2020 · 4 comments
Closed

Weird Character in Field Titles - Excel Export #308

BlierM opened this issue Apr 8, 2020 · 4 comments

Comments

@BlierM
Copy link

BlierM commented Apr 8, 2020

First comment here.
Anytime I export to Excel, all fields names that have a space in DAX are replaces with a french accent character. this has been ongoing since I have been using DAX.. and now still visible in 2.10.2.

The issue not seen on text file export. Uploaded a screen shot.
Any hints?

Capture2

Capture

@dgosbell
Copy link
Contributor

dgosbell commented Apr 9, 2020

This has always been the case. It's a side effect of how the data needs to be serialized in order to pass it from DAX Studio to Excel. The simplest work around is to use the CSV export which does not suffer from this limitation.

I can maybe have a look at replacing these back-tick characters with spaces after the data hits Excel.

@BlierM
Copy link
Author

BlierM commented Apr 9, 2020

Thx. Ok to see it is a known issue..
Yes, CSV has other benefits... or its easy to Search & Replace once in Excel.
But considering the "perceived" simplicity of the issue, I found interesting to see this visible bug being there for years.

Regards,

Martin

@dgosbell
Copy link
Contributor

dgosbell commented Apr 9, 2020

It not so much a "known issue" as I double checked the source history and it's just always been like this. Honestly I have more ideas for things to add than I have time. And I don't use the Excel output at all anymore so it's not something that worries me directly. But it's a relatively simple fix which I've just implemented so it will be part of the next release.

@BlierM
Copy link
Author

BlierM commented Apr 9, 2020

Thx!

@BlierM BlierM closed this as completed Apr 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants