Forum Discussion
Relationships
Actually, i spoke to soon. It solved some problems, players by table seems to work (Fact and DimTable).
But i'm still getting repeated numbers when pulling from revenue by table, using dimtable and calander month.
Should they all be set to "both" like so?
Thanks!
Hi
First of all, "Both" can make report slower. Remember about performance, use it only if you have to.
Next, you cannot use them in closed model cause it disable on of relationship. In your case from previous post it disable "Revenue data" with "Calendar", cause they dont know which way to filter use: by "Fact" or "Revenue data"?
Your model is closed, if you use star schema you dont connect Dim tables between itself. In your case you can make all relations to Calnedar one-direction or do Calendar table to each table you need (one for Fact and second for Revenue data).
BTW: DimPlayers have cardinality one-to-many, so one Player can have many values in Fact table. Many rows mean many dates from Calendar for one Player.
More about star schema: https://docs.microsoft.com/en-us/power-bi/guidance/star-schema
How to link multiple Fact tables:
Regards
Walter - thank you so mucn for your explanation.
1) I've followed the Star Schema approach, reduced the both ways joins as much as i beleive i can.
2) I was beating myself up trying to connect Revenue data to the Fact and Dim tables and i no realise that cant work. So ive added in a 2nd Calendar table for Revenue as you suggested and an additoinal mapping table which lets me slice by everything i need. I cant think of an occasion when i would need to use Fact and Revenue data together in one visual - same page sure, but not same visual, so I dont forsee a problem.
I guess my last question would be, is this a good approach/best practice so to speak, both performane wise or logic wise? Would there be any major pitfalls that I'm not seeing by doing this?
Again, thanks so much!
Regards
Ben