Forum Discussion
Potential bug with date() ?
I have the weirdest fix for this ... switch back the regional settings in PBI to the default.
A little annoying, but trying to figure out and fix what PBI messes up in the background is way worse.
Hi zahlenschubser ,
I have to be honest in the past (2017/2018) this would happen when we had a computer with regional settings and got a file with different regional settings and then DAX editor would become "confused". We even got problems when copying formulas to the forum because some people got the decimal separator has comma or has dot.
Since they added the functionality for the regional settings and the DAX defnitions I never seen this again. I know this will sound stupid but can you try and replace the dots by comma but be sure to add a space after the comma:
if you have 6.7 you should go to 6, 7
See if that picks up the correct values or goes back to giving you errors.
I have the weirdest fix for this ... switch back the regional settings in PBI to the default.
A little annoying, but trying to figure out and fix what PBI messes up in the background is way worse.
Have to be honest, PBI Desktop always messes up with the regional settings not sure why but it does, since back way in 2015 when it all started.
If that fixed your issue please remember to accept the solution so it can help others.
It's not really a solution if I have to undo parts of the program setup to fix an underlying coding issue, but for the sake of getting it resolved on the user side I'll mark it anyway.
Has I refered the DAX syntax and the regional settings always have been struggling together not sure why but they have.
I always keep the default for DAX syntax that way won't get into any problems.