Forum Discussion
Locale settings should not affect CSV import
The output of the M code should not be affected by application's settings.
I disagree. The application settings govern how the input is interpreted. Under different interpretations, identical data means different things and the output should reflect proper meaning. Since a CSV file doesn't contain reliable locale metadata, there isn't a straightforward way for Power Query to magically know what interpretation you expect it to use unless you specify it in the code or in the application settings.
It works as intended. If your values are comma separated, and you're using commas as decimals, how would a program know the difference between the two? They are the same character. So you told Power Query "this is Dutch" and then took the same code and said "this is English".
My gas tank doesn't show me liters instead of gallons when I drive the same car in a different country--unless I change a setting 🙂
Just kidding. I have no setting like that.
--Nate
My gas tank doesn't show me liters instead of gallons when I drive the same car in a different country--unless I change a setting
Just kidding. I have no setting like that.
I have cars with those settings. More handy with changing the speed from mph (US) to kph (Canada) though.