Relationship Status - It's Complicated! But should be simple.

[Anonymous]

Hi, 

I have an issue with my relationships, attached is a pic. Essentially i'm looking to have both the Calendar and the Team List act as filters for all the data in slicers on the visuals, however currently i'm getting only some of the slicers working at some of the time.

I'm sure there's a simple solution and i've been looking into it all I can please help!  

[Mariusz · Accepted solution]

Hi @Anonymous 

Problem is your relationships, all dimensions ( tables you will use to filter other tables ) should be set as one side with the arrow pointing towards the table that is filtered ( fact ).

Try avoiding bi-directional filters and Many to Many as explained in the article below.

https://www.sqlbi.com/articles/bidirectional-relationships-and-ambiguity-in-dax/

please see the below example of how the model should look.

Best Regards,
Mariusz

If this post helps, then please consider Accepting it as the solution.

Please feel free to connect with me.
LinkedIn

[Anonymous]

Thanks all for the help, the answer was going back to the drawing board with the model itself in order to make the Calander and Team List work. Thanks for your advice! 

[Greg_Deckler · Accepted solution]

Really difficult to tell what is going on here. I'm not super thrilled with the model you have but I do not know enough to say whether it is good or bad. Generally you want to try to go for a star schema. Very often you want to avoid bi-directional filters, that can cause problems.

I have no idea what those relationships are between the tables (what columns). Please see this post regarding How to Get Your Question Answered Quickly: https://community.powerbi.com/t5/Community-Blog/How-to-Get-Your-Question-Answered-Quickly/ba-p/38490

[Mariusz · Accepted solution]

Hi @Anonymous 

Problem is your relationships, all dimensions ( tables you will use to filter other tables ) should be set as one side with the arrow pointing towards the table that is filtered ( fact ).

Try avoiding bi-directional filters and Many to Many as explained in the article below.

https://www.sqlbi.com/articles/bidirectional-relationships-and-ambiguity-in-dax/

please see the below example of how the model should look.

Best Regards,
Mariusz

If this post helps, then please consider Accepting it as the solution.

Please feel free to connect with me.
LinkedIn