Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and a 50 percent discount on exams.
Get startedEarn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
So, I wanted to try something new and started to build a new model concept, but I have some issues with it, let me explain the basics:
1. The big table which called DB.Aggregation_combination is combination table which contains the dimension tables possible outcomes.
2. The second "layer" is the so called Results tables where I aggregate data per year/month/day.
3. The third "layer" is a kind of connector which contains the possible DISTINCT Day_IDs, Week_IDs and Year_IDs, these tables goal is to avoid to have many-to-many relationships in the model.
4. The last "layer" is a regular calendar dimension.
My problem is that when I am trying to deploy dax calculations I am recieving flat volumes applied to all hierarchy level, like in this case:
As you can see on the model, I have deployed a cross-filter option between the Dim_Calendar and Dim_Calendar_Year, Dim_Calendar_Month, Dim_Calendar_Day tables, but I am a bit confused, beacuse I don't know that what should be the most efficent way to apply this cross filtering relationships.
The other concerning point is that I don't know that why I can't use Dim_calendar fields to have proper calculation and why I receive flat volumes for all the level of hierarchy and its elements.
Please read about the basic concepts of fact tables and dimension tables. Avoid bidirectional relationships where possible. If you like you can also read about calculation groups.