Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreJoin the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. Register now
We have a CALENDARAUTO() table and we use its columns such as Month, Quarter etc in various filters. Problem is, month names are always in english and do not respond to client's locale.
How do we make month names from calendarauto() locale-aware? FYI the method described here in some other post, changing locale in model settings, (i) does not work, and (ii) we need them to RESPOND to client local, not to have a fixed locale.
Hi @Anonymous ,
I'd like to suggest you try to use 'use locate' option to manually setting content type to help query editor format your data type more accuracy.
This does not help at all as the information is way too generic.
There is a CALENDARAUTO() function which automatically creates e.g. Month hierarchy for calendar dates. Specific question, when using this Month column in reports and slicers, SHOULD it automatically match the user language or not?
@Anonymous , My advice would be to create an additional column for the month and year and try(create a hierarchy with if needed). Because if you mark this table as Date table, date will become key and you will not get Hierarchy
So out of the box, CALENDARAUTO() is not localized, and you suggest creating additional columns for month names for every language we are going to support? And re-designing every report page? I am not sure wherever you are even serious...
Check out the April 2026 Power BI update to learn about new features.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
| User | Count |
|---|---|
| 48 | |
| 46 | |
| 41 | |
| 20 | |
| 17 |
| User | Count |
|---|---|
| 70 | |
| 69 | |
| 32 | |
| 27 | |
| 26 |