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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
Anonymous
Not applicable

1 to many relationship providing wrong results in visualization

Hello. I have the following two tables:

Table 1: Position Details

Table 2: Survey

 

There is a M:1 Relationship from Table 1 to Table 2.

When I put fields from both tables into a visualization, aggregations get messed up. 

For example, Table 2 only contains data belonging to specific business units (that's a field in Table 1).

But when I present data in a graph, a number field from Table 2 gets aggregated across all business units in Table 1. See below

 

mmiculcy_0-1632250769709.png

My expectation is to see the average for only the business units that are actually related to table 2.

1 REPLY 1
HotChilli
Super User
Super User

When you see something like this either :

a) the relationship is not working (wrong data type or no matching data) OR

b) the relationship is the wrong way round.

 

I suspect it's b) but I can't quite work out which fields from which table are in the visual.

This part "M:1 Relationship from Table 1 to Table 2" implies Table2 is filtering Table1. Is that what you want?

You want the dimension table to filter the fact table.

 

Is that enough to get you closer to the problem?

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.