Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now

Reply
cristianml
Post Prodigy
Post Prodigy

Relationship issue

Hi,

I have an issue with a relationship related to "Location". I can't find the error in this case: 

 

RELATIONSHIP.png

In the Dashboard the two columns "Lcations" should show same values/location in each line: 

dashboard.png

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.

1 ACCEPTED SOLUTION
d_gosbell
Super User
Super User

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.

View solution in original post

2 REPLIES 2
d_gosbell
Super User
Super User

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.

Thanks @d_gosbell ,

 

Works perfect. I just forgot to update with April data. 

Thanks again ! 🙂

 

Helpful resources

Announcements
New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

March Power BI Update Carousel

Power BI Community Update - March 2026

Check out the March 2026 Power BI update to learn about new features.