Forum Discussion
M:1 relationship not observed
Continued Contributor
Usually when the cross filter direction is disabled or it can't be changed, it's usually because of another relationship that exists between other tables. Try setting the cross filter direction to "single" for some of the other relationships if you have them and see if cross filter for this particular relationship can be changed.
does power BI desktop auto assign relationships if the two tables have common column names?
In 'Edit relationship' I can only see those two columns highlighted (and'Manage Relationships' modal only shows these two columns in parantheses), but T2 has another column called 'id'. It is not specified in the relationship though.
- wonga
ekinmur Yes, by default PowerBI auto detects relationships between tables. Sometimes this auto-detection may result in an incorrect relationship, so it's always best practice to double check it just to make sure. 9 times out of 10 though, the auto detection is correct.
Are the auto detected related columns between the two tables correct or not? If not, you can modify the relationship to what you think it right and Power BI will let you know if it's valid.
wongaso T1 has an id column and T2 also has an id column, but the relationship between the two is not correct. There is a relationship between the calculated column Column in T2 and id in T1, which I specified and is the only relationship showing in the relationship manager modal.
If power BI is implicitly defining a relationship between T1[id] and T2[id], it is not showing in the editor and I thus don't know where to disable it.
- wonga
ekinmur Okay, so it looks like there were no relationships that were automatically made upon loading data into PBI. If the only relationship you see in the relationship manager is the one you created, then it shouldn't be a problem. You should be able to choose the "Both" option for cross filter direction since there are no other relationships that could cause conflicts.