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.
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.
I disagree.
What if you want to import several cav each with its own locale
Or one that is not standard
The obvious way would be the option for the user to define decimal point character for each csv import , the same way he defines delimiter.