The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event! Join us in Stockholm, Sweden from September 24-27, 2024.
2-for-1 sale on June 20 only!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
Dear all,
I have two fact table (Sales Table, Gift Table) and they have common look up dimension table (Customer, Product, Calender, etc).
I would like to filter out dimension based on fact, like "find customer who has bought certain amount of product A while received gift before'. This, I believe, would require a bidirectional filtering. And when I change to bidirection, Power BI would not allow it, saying there is ambigious filtering path.
My current solution would be disable/switch to "single" relationship when needed. Can you guys share your experience on design the data structure with multiple fact table? Thank you.
A schema can have one or more facts, but these facts are not linked by any key relationship. It is best practice not to join fact tables in a single query.Please refer these two very good articles:
Three ways to drill across by Chris Adamson
and
Should of the Warehouse - Drilling Across by Ralph Kimball
(from Stack overflow)
@KeithChu,
Please check my reply in the similar thread below. If you still have questions, please share a screenshot about your relationships in the data model.
https://community.powerbi.com/t5/Desktop/Data-model-loop-cant-point-2-transaction-dates-to-DateTable...
Regards,
Lydia
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 June 2024 Power BI update to learn about new features.
User | Count |
---|---|
99 | |
93 | |
81 | |
63 | |
56 |
User | Count |
---|---|
248 | |
123 | |
111 | |
78 | |
74 |