DAX formula localization "conflict"

[MrGorkajuice]

Hi,

I just installed Power BI on a new PC, and I seem to have ended up with some strange annoying combination of localizations - both my decimal seperator and my DAX argument seperator is comma. That means that the following formular is invalid:

Test=IF(1=1, true)

... because the comma is interpreted as a decimal seperator.

The fix:

Test=IF(1=1,0, true)

This is... unacceptably annoying. In Excel on the same PC, DAX arguments are seperated by semicolon, which is the expected behavior based on my Windows level regional settings.

Any idea what could lead to the above Power BI-specific confusion?

[MrGorkajuice]

Accidental double posting of https://community.powerbi.com/t5/Desktop/DAX-formula-localization-quot-conflict-quot/m-p/1060929

[amitchandak]

@MrGorkajuice , Is this not same you posted yesterday and resolved language setting

https://community.powerbi.com/t5/Desktop/DAX-formula-localization-quot-conflict-quot/m-p/1060929

[MrGorkajuice]

Oh right, sorry. I got an error message when I posted the question and couldn't find it... 

[MrGorkajuice · Accepted solution]

I found a fix.

It seems the issue occurs whenever my Windows Language settings uses "English (Denmark)" as Default input language. My own working theory is that this setting uses the english part to determine the parameter seperator in DAX functions, but the danish part to determine decimal seperator.

I can now switch between consistent english behavior (dot as decimal seperator and comma as parameter seperator) by using "English (United States)", or consistent danish behavior (comma as decimal seperator, semicolon as parameter seperator) by using "Dansk".

[amitchandak]

@MrGorkajuice , I think that is under regional settings.Choose the country that should change the setting

https://subscription.packtpub.com/book/big_data_and_business_intelligence/9781788290142/1/ch01lvl1se...

[MrGorkajuice]

Didn't help 😞

In my "Global Regional Settings", I am only able to change "Application language" the language used by the Power BI UI, and "Model language" which seems to be only about standard formatting of dates, etc.

I have played with both, and neither seem to have any effect on the evaluation of DAX expressions - I can't change neither decimal seperator nor function argument seperator through either of these settings.

[az38]

@MrGorkajuice 

there are some regional localization issues in PBI

I have a similar issue here https://community.powerbi.com/t5/Issues/Regional-settings-and-Month-names/idi-p/1008637