Forum Discussion
Relationship Functions
- 2 years ago
Your data model has to follow the business problem. That sometimes means you need to adjust your data model. For example you may have a fact table with ticket information including Opened Date and Closed Date. Now you want to know for each month how many tickets were opened in that month and how many were closed. You can't answer that with a regular data model, you need to employ USERELATIONSHIP to temporarily modify the link between the calendar table and the fact table.
Kudos for trying to learn about these, but true learning comes from needing to apply these functions in your business scenario.
Your data model has to follow the business problem. That sometimes means you need to adjust your data model. For example you may have a fact table with ticket information including Opened Date and Closed Date. Now you want to know for each month how many tickets were opened in that month and how many were closed. You can't answer that with a regular data model, you need to employ USERELATIONSHIP to temporarily modify the link between the calendar table and the fact table.
Kudos for trying to learn about these, but true learning comes from needing to apply these functions in your business scenario.