Forum Discussion
Help linking tables together - ambiguity
- 7 years ago
Anonymous based on your requirement, i think the relationship between employee and interaction is not required. and make relationship active between org and employee.
- Anonymous7 years ago
Anonymous -
If I understand your requirements correctly, you could remove the relationships to org, and instead make a relationship between org and interactions.
So interactions would be the fact table, and org, emp, and client are dimension tables.
Then you can use DISTINCTCOUNT on empid and clientid from the Interactions Table, and use org name from the Org table.
Cheers!
Nathan
Anonymous -
If I understand your requirements correctly, you could remove the relationships to org, and instead make a relationship between org and interactions.
So interactions would be the fact table, and org, emp, and client are dimension tables.
Then you can use DISTINCTCOUNT on empid and clientid from the Interactions Table, and use org name from the Org table.
Cheers!
Nathan
- Anonymous7 years agoNot applicable
Thank you all! Yes I didn't really need that relationship to exist in the example above.
From browsing around the forum, another solution that works well is using the "userelationship" function to force an inactive relationship to be active.