Forum Discussion
Get selected value USERELATIONSHIP (no aggregation)
I have a simple model:
dim Employee --> employee_id + Name
fact Complaints --> complaint_id + registror_id + executor_id + duration.
Registor ID is the Employee who made the complaint
Executor ID is the employee to solve the complaint.
My idea this can be done by make an active relationship between employeer_id and registor_id to show the Registors (put dim Employee [Name] in a table column. Also make an inactive relationship between employee_id and executor_id:
And I wrote a measure to show the Executor:
When i put on complaint ID + dim employee [Name] + Measure Executor i get this repeated:
ID Registror Executor
1 John Doo | Marge Peterson
2 John Doo | John Doo
Can this be done with the CALCULATE / SELECTEDVALUE / USERELATIONSHIP?
- so best practice would be to make multiple dim Employee tables? (Just reference in the Power Query)
I found a link which discusses this:
https://community.fabric.microsoft.com/t5/Desktop/Dealing-with-multiple-references-to-the-same-table-without/td-p/2429212
simply the model and create a proper star schema it would be recommended to have two user tables, one will be Sales Owner Users and the other Relationship Owner Users. There really isn't a need to create complexity in measures / visuals / report with a single user table (which usually only have a few hunderd or a few thousand records)So it would be best practice to make multiple references! I probably was overthinking this 🙂
2 Replies
- joris-kempenFrequent Visitor
I found a link which discusses this:
https://community.fabric.microsoft.com/t5/Desktop/Dealing-with-multiple-references-to-the-same-table-without/td-p/2429212
simply the model and create a proper star schema it would be recommended to have two user tables, one will be Sales Owner Users and the other Relationship Owner Users. There really isn't a need to create complexity in measures / visuals / report with a single user table (which usually only have a few hunderd or a few thousand records)So it would be best practice to make multiple references! I probably was overthinking this 🙂
- AnonymousNot applicable
Hi joris-kempen ,
Glad to see that you found the documentation to solve your problem, it will help other users on the community who have the same problem!Best regards,
Albert He