Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi,
I have an issue with a relationship related to "Location". I can't find the error in this case:
In the Dashboard the two columns "Lcations" should show same values/location in each line:
In the 1st table the first column "Location" corresponds to the List Location, and the second one to the query ("Ad hoc costs") column.
In the 2d table the first column "Location" corresponds to the List Location, and the second one to the query ("cost center") column (see relationship).
Could you help me to find the error here?
Thanks.
Solved! Go to Solution.
As a general rule I always hide the column on the "many" side of a 1 to many relationship as any time you have more than fact table in a complicated model using the column from the many side will always cause this sort of data explosion due to the way filters propogate along relationships. From the limited snapshot we can see I think if you only ever use 'List Location'[Location] then everything should work OK.
Note that setting the crossfilter direction on the relationship may at first appear to "solve" this issue. But doing so will negatively impact the performance of the model and with the number of relationships you have in your model I can almost gurantee that adding a bidirectional filter will produce incorrect results.
As a general rule I always hide the column on the "many" side of a 1 to many relationship as any time you have more than fact table in a complicated model using the column from the many side will always cause this sort of data explosion due to the way filters propogate along relationships. From the limited snapshot we can see I think if you only ever use 'List Location'[Location] then everything should work OK.
Note that setting the crossfilter direction on the relationship may at first appear to "solve" this issue. But doing so will negatively impact the performance of the model and with the number of relationships you have in your model I can almost gurantee that adding a bidirectional filter will produce incorrect results.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 40 | |
| 35 | |
| 34 | |
| 31 | |
| 28 |
| User | Count |
|---|---|
| 136 | |
| 102 | |
| 68 | |
| 66 | |
| 58 |