Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowData Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more
Hello,
I have some problems by using userelationship in my data model. I am not sure why it is not working. I read a lot of articles in the forum but found nothing. Hope you can help.
My data model has the following form:
The relations are:
sn_incident_task ( task_number) <-> sn_task_sla (task_number), active
sn_incident_task (inc_number) <- sn_incident_metric (inc_number), active
sn_incident_metric (inc_number) -> sn_task_sla (inc_number), inactive
Lets take this simple Calculation to show my problem. I want to create a new column that draw a column from another column.
1. Measure with userelationship:
As you see in the picture, both columns are identical. (Beacause of sensitive data, I filter for other and blank.)
The result of the calculation is wrong. It is everytime use the active relation and not the inactive. For other inactive relations userleationships works.
What did I wrong?
Greetings
Christian
Solved! Go to Solution.
@_-Christian-_ - The relationships in your screenshot are a mess. this model definitely has ambiguous pathways for filtering to travel and is very unlikely to give correct answers even if USERELATIONSHIP worked.
I can see you have an active one-to-many relationship from incident_metric to sn_incident_task, then an active one-to-many relationship from sn_incident_task to sn_task_sla - the calculation is following this routeway, and therefore USERELATIONSHIP does not need to be invoked.
I suggest you read up on Star Schema's in Power BI. I also have a useful blog on the impact of relationships - https://triangle.im/power-bi-mistake-7-why-bi-directional-relationship-issues-will-cause-headaches/
If this helps, please accept as the solution, it helps with others facing the same challenge.
@_-Christian-_ - The relationships in your screenshot are a mess. this model definitely has ambiguous pathways for filtering to travel and is very unlikely to give correct answers even if USERELATIONSHIP worked.
I can see you have an active one-to-many relationship from incident_metric to sn_incident_task, then an active one-to-many relationship from sn_incident_task to sn_task_sla - the calculation is following this routeway, and therefore USERELATIONSHIP does not need to be invoked.
I suggest you read up on Star Schema's in Power BI. I also have a useful blog on the impact of relationships - https://triangle.im/power-bi-mistake-7-why-bi-directional-relationship-issues-will-cause-headaches/
If this helps, please accept as the solution, it helps with others facing the same challenge.
Hello,
It might be good to use a measure instead of a column, but even in the event of using a column consider the following dax instead of use relationship
table 45
table 46
relation between ur1
46 Column = RELATED('Table (45)'[Value])
46 Column 2 =
This will give expected result without added relationships
I hope this post helps to solve your issue and if it does consider accepting it as a solution and giving the post a thumbs up!
My LinkedIn: https://www.linkedin.com/in/n%C3%A4ttiahov-00001/
Proud to be a Super User!
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |