Forum Discussion
Multiple Fact Tables also act as Lookup Tables
If I have two tables, one with Opportunities and one with Sales where there is already an established link (the opp id), is there best practice for handling when these data tables also act as lookup tables.
If I want to see the sales that came from opportunities created before the 22nd of Jan, I COULD do this by sorting the opps table, OR I could make a seperate lookup table with the opp and the date created and sort that with a relationship to sales. Are there resources on handling these scenarios? I could also JOIN the opps information in the query with sales, but that seems more intensive than the other ways.
Is the relationship that you refer in the post a many-to-many or a one-to-many, if it's a one-to-many then you just need to use the values from the one side two make the context and then add the data from the other table. If this is a many-to-many, I believe the best option is to create a bridger table with distinct values to pick up the information from both the tables.
2 Replies
- MFelix
Super User
Is the relationship that you refer in the post a many-to-many or a one-to-many, if it's a one-to-many then you just need to use the values from the one side two make the context and then add the data from the other table. If this is a many-to-many, I believe the best option is to create a bridger table with distinct values to pick up the information from both the tables.
I think you are correct after further research. I think that (in time) I will detangle the reports I have been assigned and try to create some bridge tables as many of the values are created from referencing and filtering data tables.
