Forum Discussion
Problems with Locale
Hi Anonymous,
This is a pretty interesting use-case and I'm not aware of a feature-based way to do it in terms of granular locale setup.
As an English-speaker, I often find myself after something similar so that I can test internationalisation of custom visuals when I develop them, so that I can verify number formatting etc. in different locales without getting stuck in a UI I can't always get back out of easily if I change the language as a workaround.
I had a quick read through the ideas site but nothing has been raised, so perhaps it could be worth creating this as an idea for future development? If so, let me know and I'll vote on it 🙂
For now, if you want to specify dates in a particular format, while using an application locale that doesn't have these as standard, then I think that custom formatting strings are going to be your best option as a workaround (if you haven't already considered them):
I'm not sure if this will solve your particular requirements, but might give you an alternative approach to consider.
Good luck!
Daniel
If my post solves your challenge, then please consider accepting as a solution to help other forum members find the answer more quickly 🙂
Hi Anonymous,
This is a pretty interesting use-case and I'm not aware of a feature-based way to do it in terms of granular locale setup.
As an English-speaker, I often find myself after something similar so that I can test internationalisation of custom visuals when I develop them, so that I can verify number formatting etc. in different locales without getting stuck in a UI I can't always get back out of easily if I change the language as a workaround.
I had a quick read through the ideas site but nothing has been raised, so perhaps it could be worth creating this as an idea for future development? If so, let me know and I'll vote on it 🙂
For now, if you want to specify dates in a particular format, while using an application locale that doesn't have these as standard, then I think that custom formatting strings are going to be your best option as a workaround (if you haven't already considered them):
I'm not sure if this will solve your particular requirements, but might give you an alternative approach to consider.
Good luck!
Daniel
If my post solves your challenge, then please consider accepting as a solution to help other forum members find the answer more quickly 🙂
Thanks for that video with guy-in-cube, it helped. I wasn't aware that you could set column/measure format in the model view. I was always working in the report view and changed format there.
However, I did notice a few inconsistent behaviours in the client.
I have a datetable defined as:
TimeLine - Report =
var basecalendar = SELECTCOLUMNS(dates,"ReportDate",[Date])
return
GENERATE(
basecalendar,
var integerdate = FORMAT ( [ReportDate], "YYYYMMDD" )
RETURN ROW("DateAsInteger", integerdate)
When I edit the columns for this table in "report view" I get the problems I initially described, using the new ribbon prohibits me from choosing the date format "yyyy-MM-dd".
When I edit the columns in "model view" I do have the option to choose "yyyy-MM-dd" but when client finishes executing the change, the format is still listed as "*yyyy-MM-dd". I can fight all I want, it still switched back. I am able to use custom option here though.