Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Is there a way to use locale-aware date hierarchies - specifically, quarter and month names - within visual elements?
Problem is, once you create CALENDARAUTO() table with built-in hierarchy, it gets created according to current locale of the .pbix file. If it was english, you will have "Qtr1", "Qtr2" for quarters, "January", "February" for months and so on. It will not change and stay the same for the client who comes to use the report using any other locale: he will get system menus in his preferred locale, but not the quarter/month names - they will remain constant.
What we want is quarter and month names being displayed in the client's locale. Is this not supported?
Hi @Anonymous,
Nope, you can't modify the default date hierarchy locale that analysis by power bi itself. In my opinion, I'd like to suggest you create a calendar table and add custom columns to extract and convert to different data region language, then use these fields with common date fields to create custom hierarchy
Regards,
Xiaoxin Sheng
Creating custom column cannot be a solution, because it is simply not manageable. First, it would require to create literally dozens of custom columns for each of the dozen languagaes. Second, it is unclear how would the design look in this case. Imagine we have a monthly slicer that has to have month names on it. How do we design it so it has italian names for client with italian locale, russian for russian client and english for english? As far as I can see, there is no solution to this.
So short answer, platform does not support locale-aware period names for key feature that is promoted as a pillar for sorting out all date-related information - calendarauto() tables.
I do not want to CHANGE language of quarter/month of date hierarchy. I want this language to be locale-aware, as many other elements of power bi. So first link answers to the different question, while second link being completely irrelevant.
Also would you be so kind to remove this clutter from your signature please - it takes way too much space on the screen while not containing any helpful information:
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
Check out the October 2025 Power BI update to learn about new features.