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
Hi,
they say: create only one dim_time table for all facts. So:
Now I have one dim_time which relates to multiple fact tables. The problem is, when I use this dim_time for filtering to a specific date it will filter all the other facts for that date as well.
When I want to filter only the registrations for a specific date and get all the sales for these customers who registerd at that date.
Or get all the sales for a specific date and see the registrations for the customers who did that sells.
Do I need two dim_time-dimensions for that?
I am using the SSAS and my Power BI would use this model after it is done.
Solved! Go to Solution.
You can write measures that remove filters. You can also set the time relationships up as inactive and only activate them within certain measures (USERELATIOINSHIP).
If you need to control filters for the fact tables independently and simultaneously with slicers, then it may be better to have multiple time dimensions.
You can write measures that remove filters. You can also set the time relationships up as inactive and only activate them within certain measures (USERELATIOINSHIP).
If you need to control filters for the fact tables independently and simultaneously with slicers, then it may be better to have multiple time dimensions.
Okey, than I was right with the two dimensions , one for each time.
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 |
---|---|
110 | |
78 | |
66 | |
52 | |
51 |
User | Count |
---|---|
121 | |
116 | |
77 | |
64 | |
63 |