Forum Discussion
How would you model this ?
curiouspbix0 Yes sir
curiouspbix0 totally, try to shoot for star schema, and there is no need to do the merging, you can still have city dimension as a separate table and relate to these two tables. there are many ways to achieve what you are trying to do but one thing is for sure, you don't need to merge or create a calculated table.
I would ❤ Kudos if my solution helped. 👉 If you can spend time posting the question, you can also make efforts to give Kudos whoever helped to solve your problem. It is a token of appreciation!
Many to Many join is what I was trying to avoid along with Bridge tables as the need is a LEFT OUTER actually.
So my options for left outer join are 1. Use bridge table
2. Write DAX
What is the best practice to enable multple left outer joins from masters to transactional ?
curiouspbix0 Yes many-to-many can be expensive, doing bridge table is the way to go, and then any requirement to measure the data can be controlled by DAX.
I have developed very complex DAX measures on very complex data models to meet some complicated business requirements, of course sometimes you need to check the performance of your measures to make sure measures are optimized.
I would ❤ Kudos if my solution helped. 👉 If you can spend time posting the question, you can also make efforts to give Kudos whoever helped to solve your problem. It is a token of appreciation!
So you would rather use bridge tables & Dax to Power Query processed dataset that would result one table with master and transactional together which is obviously better on report refresh visual runtimes with a trade off on backend ETL on Power query.
curiouspbix0 Yes sir