The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
I have a matrix that I created that used a date dim table date field as one of the values. I wanted to add some previous months calculations to the matrix. In order for my dax to work properly, I marked the date dim table as a date table. Now however, The date field from the date dim table no longer shows a time hierarchy (year-> quarter -> month). it only has stagnant dates (1/1/2023). If you use the date field from the date dim table in a visual, does marking the date dim table as a date table prohibit the drill down feature? After marking the date dim table as a date, I now have this icon next to the field.
Has anyone found a way to mark the date dim table as a date table, but still be able to use it in visuals that will allow the drill down feature?
Solved! Go to Solution.
Thanks for the response, @lbendlin. That was my issue. It was not automatically creating a hierarchy when I put a date field on the X axis. I was able to solve this issue for anyone else who might have the same problem when using a self created date dim table. Apparently if you mark a date dim table as a calendar table, it automatically removes the time hierarchy. You can create your own hierarchy for the time within your date dim table. However if your month field in the date dim table is just a text string like "January", it will sort the months alphabetically instead of chronologically. To circumvent this issue, you will also need to add a month field that contains values as a whole number (january would be 1, February 2 etc). You can then sort the text string month field by the whole number month field in the data view, which will allow for the month text strings to be displayed chronologically in your visual.
Thanks for the response, @lbendlin. That was my issue. It was not automatically creating a hierarchy when I put a date field on the X axis. I was able to solve this issue for anyone else who might have the same problem when using a self created date dim table. Apparently if you mark a date dim table as a calendar table, it automatically removes the time hierarchy. You can create your own hierarchy for the time within your date dim table. However if your month field in the date dim table is just a text string like "January", it will sort the months alphabetically instead of chronologically. To circumvent this issue, you will also need to add a month field that contains values as a whole number (january would be 1, February 2 etc). You can then sort the text string month field by the whole number month field in the data view, which will allow for the month text strings to be displayed chronologically in your visual.
See it as a good thing. Your "drill down feature" was adding ungodly amounts of extra calendar tables to your semantic model (one for each date field). That's why you should always disable "Auto Date/Time".
You can create your own hierarchies if you want, but most visuals do it for you when you put the date field on the x axis.
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
User | Count |
---|---|
3 | |
3 | |
2 | |
1 | |
1 |