Forum Discussion
Represent Different One to Many [Received Dates] on Same Timeline
Here's a preliminary view of how the data model could be structured
Note that the relationship between Enquiry and Issues is inactive (and practically useless) since it would introduce ambiguity. It will be easier to use TREATAS in this scenario.
The main question is - what is your focus on? Is it a calendar view ("what happened this month?") or a entity view ("What happened to Enquiries over time?")
Super UserHere's a preliminary view of how the data model could be structured
Note that the relationship between Enquiry and Issues is inactive (and practically useless) since it would introduce ambiguity. It will be easier to use TREATAS in this scenario.
The main question is - what is your focus on? Is it a calendar view ("what happened this month?") or a entity view ("What happened to Enquiries over time?")
I kept researching and managed to get it working, both in the 1 to many or denormalised form. (those files uploaded and replaced the previous powerbi files).
Really appreciate your redirect questions, they are making me think and explore.
The goal would be to see what happens each month. I am using the one to many relationship to allow the user to click an enquiry record and then filter the issue records to provide a related snapshot. So in terms of being useless, if I understand, I would agree, given that the measures would apply USERRELATIONSHIP - is my understanding correct?
So, if the focus is to represent what happens each month, would it better to denormalise into one table?
TREATAS - wow! just had a quick look at that 🙂
- lbendlin
There is another option - you can change the search direction to make the relationship bidirectional between one of the fact tables (Enquiry) and the dimension table (Dates). However that is frowned upon as it will likely create trouble down the road.
Thank you.
Is there any particular book that you can recommend regarding data model design in general?
- lbendlin