Forum Discussion
Relationship not being applied to some visuals
- 7 years ago
Hi cparker4486,
From looking at your relationship, I believe that the direction between the tables is the issue. If you look at the arrow direction from header to line, this means that the header table can filter the line table, but not the other way around, i.e. the arrow only goes one way. This blog post may explain it better than I can.
You have a couple of solutions (in order of simplicity):
- Change the relationship direction from single to bi-directional. While this is possible, it is often discouraged in favour of...
- Re-designing the model.
- Because the header and line tables are essentially 'fact' tables, it is advised to have a 'dimension' table (or similar) that bridges them so that filtering works more intuitively, or, replace both tables with a single table so that you are working at the right level of grain. This latter option might not be ideal depending on your scenario.
- Again, RADACAD have a great series on these modelling concepts, if you've not come across them to date. This is the most recent post, but it's good to read them through from the beginning (all referenced in the linked post).
- The 'right' model will vary depending on your particular use case but the above dimensional modelling principles are a great way to structure your data so that it is its most malleable.
I hope this sets you off in the right direction. Good luck!
Daniel
Hi cparker4486,
From looking at your relationship, I believe that the direction between the tables is the issue. If you look at the arrow direction from header to line, this means that the header table can filter the line table, but not the other way around, i.e. the arrow only goes one way. This blog post may explain it better than I can.
You have a couple of solutions (in order of simplicity):
- Change the relationship direction from single to bi-directional. While this is possible, it is often discouraged in favour of...
- Re-designing the model.
- Because the header and line tables are essentially 'fact' tables, it is advised to have a 'dimension' table (or similar) that bridges them so that filtering works more intuitively, or, replace both tables with a single table so that you are working at the right level of grain. This latter option might not be ideal depending on your scenario.
- Again, RADACAD have a great series on these modelling concepts, if you've not come across them to date. This is the most recent post, but it's good to read them through from the beginning (all referenced in the linked post).
- The 'right' model will vary depending on your particular use case but the above dimensional modelling principles are a great way to structure your data so that it is its most malleable.
I hope this sets you off in the right direction. Good luck!
Daniel
- cparker44867 years ago
Helper III
This explains a lot. I've come across this issue multiple times in the past with different data and I'll always ended up working around it. Now I'll have a chance to fix this properly!
I wonder if this will make Power BI crash less...? That would be a nice side effect!