Our end users are complaining that when they export data from PowerBI and open it in Excel, the text with cyrillic letters is not readable. This is due to the fact that the export is in UTF-8 and one cannot force the Excel to recognize the encoding. Therefore the workaround is - save the file in csv, open it with a text editor, save it as ANSI and then open it with Excel.
This is not an issue for an IT guy, however in our case Power BI is used from non-IT C-level managers and the above steps are too complicated and annoying for them.
Does anyone have an idea how to solve this? I have read the Excel forums, have tried wth different browser options - unfortunately with no success.
Three weeks ago, something was changed in csv file. Now line with "sep=," is deleted when enything is exported from Power BI. This mean that the file can't be open in Excel. It is always opening as a text not divided into column. User have to import data from text to Excel which is very annoying. How to change it that Excel will open the file as was before change?
I think sep= is removed because it cause Excel to ignore BOM in the file which caused other issues.
For your scenario, you can change the list separator in Window.
I believe 'sep=' instruction was removed because it will make Excel to ignore the Byte Order Mark which breaks many scenarios.
For your situation, you could workaround the issue by changing separator in windows control panel
For last 3 weeks file exported to csv was changed and line with "sep=," is deleted. Now Excel can't open it directly, always have to import from text to have it properly opened. Do anybody know how to change it that Excel can directly open file as was 3 weeks ago?
Why doesn't power bi export it in ANSI?? this way wouldn't be any problem, would it? I think changing it in power bi would resolve it, so lets say them , I have a ticket with this case but as more tickets more possibilities to be solved.... thanks
If the problem is recognized by the PowerBI team, a solution can be found and delivered.
And the problem exists - the current export is clumsy for those unlucky to have data in encoding different from Win-1252.
Well, what I am trying to say is that instead of asking Power BI to have workaround which have 0 workaround in some situation.
You could probably vote for the following:
Which probably would benefit a larger audience, since lots of people complain about that:
just my $0.02 🙂
Have the users try this:
Hi @Greg_Deckler and thanks for the reply.
The default application for opening csv files is set to MS Excel. Because of this the exported data file is opened directly with Excel and the cyrrilic letters are shown as gibberish.
I was thinking of setting the default csv application to Notepad, then the users could copy the text lines (all but the first), open Excel and from Paste->Use Text Import Wizzard paste the text into the sheet. Unfortunately I am sure the users will not like it.
Yeah, understood, either way it is fairly complex for the user versus "double-click the file". Not sure of a way around it short of writing VBA code of some sort.
Hi, we have bag that describe below:
We get the first row the letters [sep=,] its prevent us to open file in excel as you instructed us.
Take a look at the September 2023 Power BI update to learn more.
Join Microsoft Reactor and learn from developers.
Join us for a free, hands-on Microsoft workshop led by women trainers for women where you will learn how to build a Dashboard in a Day!
Join us Oct 1 - 6 in Las Vegas for the Microsoft Power Platform Conference.