Forum Discussion
When connecting to a csv source, data shows wrongly encoded
Dear team,
I have been using csv source for many of my reports untill today for one of the csv file, I am getting encoded data. I read online about the data having special characters could cause some problem but all values are within "" plus it is semi colon dxelimitted files but power BI or rather power query is not recognizing as a delimitter. Here is how it is coming. Any clue what settings I need to change to get this in readable format ?
Thanks
Hi simmi21 ,
When testing with the sample data you have provided, seems like it works fine in Power BI:
The .txt file also works:
Perhaps you can re-create a txt file with data to try to connect it in Power BI to check, then change to .csv file to re-connect to check it again.
If the data just show one column in the navigator, you can click transform data and split by delimiter as @ AlexisOlson manually, use the first row as the header.
Best Regards,
Community Support Team _ Yingjie Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
12 Replies
Could you try changing the "File Origin" to 1200 instead of 1252?
Nope, doesn't help.
Can you provide a CSV sample (keep it small and cut out anything sensitive) that we can reproduce this with?
Here how the sample data looks
Period (months);"Vehicle Units";"Vehicle Build Region";"Vehicle Brand";"Vehicle Model (CA)";"Price Class";"Vehicle Dev.-Code";"Version";"Period (quarters)";"Period (semester)";"Period";"Market Volume";"Region";"Global Region";"Planning Region";"Customer";"Customer Group";"Vehicle Model ";"Region (sales)";"Global Region (sales)";"Planning Region (Sales)";"Division";"Vehicle Segment";"Vehicle Model";"Conti Volume";"Article Code";"Article Description";"efg";"Sales";"Production Plant";"Rim" 1;4173;"CHINA";"abc";"qwer";;"abc;"2021 FC 00+12";"Q1";"H1";"2021-01-01";205;"CHINA";"APAC";"CHINA";"CHINESE OEM OTHER";"CHINESE OEM";"SEV00h";"CHINA";"APAC";"CHINA";"xyz";"";"";0;"";"";0;0;"";"" 1;27873;"INDIA";"pqr";"rewq";;"abc";"2021 FC 00+12";"Q1";"H1";"2021-01-01";139;"INDIA";"APAC";"INDIA";"OTHER KEY ACCOUNTS";"OTHER KEY ACCOUNTS";"DOST";"INDIA";"APAC";"INDIA";"xyz";"";"";0;"";"";0;0;"";"" Hi simmi21 ,
When testing with the sample data you have provided, seems like it works fine in Power BI:
The .txt file also works:
Perhaps you can re-create a txt file with data to try to connect it in Power BI to check, then change to .csv file to re-connect to check it again.
If the data just show one column in the navigator, you can click transform data and split by delimiter as @ AlexisOlson manually, use the first row as the header.
Best Regards,
Community Support Team _ Yingjie Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
The settings to change have to do with the File Origin box. But without knowing anything more about your csv file than the screenshot you shared, it's not possible to tell you how to change it.
You could try a trial and error approach; or you could provide more information about the csv file.
I tried to play around with the regional settings and here is how it looks, good news I don't see the encoding but still it is not delimitted the way it should.
When you open the CSV file with Excel or a text editor, do you see the unencoded data?
yes, now its is unencoded but all in one column, the delimtter (which in my case is a semicolon ) is not working. This is how it is coming now :
Perhaps what looks like a semicolon is not a semicolon, but another character that appears similar. Can you please examine the characters to ascertain exactly what the character code is? You can do this in Excel with the UNICODE function; or using a Hex editor on the file.
