Forum Discussion
Multiple Fact Tables/Granularities - drill-through without a fact-fact relationship?
Anonymous
a good practice to know if the facts of the two tables can be set in one fact table if to follow these two conditions :
rule1 :
When 2 or more facts describe events that do not take place at the same time, they describe different processes.
when two or more facts do not occur simultaneously, they represent different processes. thus they need their own fact table.
rule2 :
When two facts exhibit different grain, they represent different processes. thus , different fact tables.
know i would suggest to create a dimtickets and link it to both fact, this way you remove the relation between the two facts.
+ you can relate calendar to ticket action on Actioncreatedon column .
let me know if this helps .
If my answer helped sort things out for you, i would appreciate a thumbs up 👍 and mark it as the solution ✅
It makes a difference and might help someone else too. Thanks for spreading the good vibes! 🤠
So something like this..?
And I can see the relationship between DIM_tickets and FCT_tickets defaults to di-directional, so filters on ticket DIM tables will propogate over to FCT_TicketActions - is that correct?
I can see that the relationship between the dimtickets