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
ysherriff
Resolver II
Resolver II

Many to One relationships

Hi all,

 

I have a table titled “Marketing Assets” with many values for the column “Marketing Assets”. I have another table titled “Marketing Assets TopN” with only unique values for Marketing Assets.

 

I am wondering and need help to know why Power BI is not allowing me to make this a many to one relationship? It is forcing a Many to Many and I can’t do formulas accurately. Any help is appreciated.

 

 

ysherriff_2-1654789931992.png

 

 

 

2 ACCEPTED SOLUTIONS
Greg_Deckler
Super User
Super User

@ysherriff I believe it should be One to Many, not Many to One. The order of your tables matters. The other possibility is that you have 2 items in your "unique" table that DAX does not consider unique. Remember that DAX is case insensitive so "A" is the same as "a" as far as DAX is concerned.


@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
The Definitive Guide to Power Query (M)

DAX is easy, CALCULATE makes DAX hard...

View solution in original post

ysherriff
Resolver II
Resolver II

I found the answer on Enterprise DNA forum:

 

"The reason why it’s forcing to create a “Many-to-Many Relationship” is because you’ve “NULL” values in both the sides of the table. Power BI is not able to distinguish the null value as a each unique value and therefore, it establishes or creates a “Many-to-Many Relationship” in this case."

 

Thank you.

View solution in original post

2 REPLIES 2
ysherriff
Resolver II
Resolver II

I found the answer on Enterprise DNA forum:

 

"The reason why it’s forcing to create a “Many-to-Many Relationship” is because you’ve “NULL” values in both the sides of the table. Power BI is not able to distinguish the null value as a each unique value and therefore, it establishes or creates a “Many-to-Many Relationship” in this case."

 

Thank you.

Greg_Deckler
Super User
Super User

@ysherriff I believe it should be One to Many, not Many to One. The order of your tables matters. The other possibility is that you have 2 items in your "unique" table that DAX does not consider unique. Remember that DAX is case insensitive so "A" is the same as "a" as far as DAX is concerned.


@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
The Definitive Guide to Power Query (M)

DAX is easy, CALCULATE makes DAX hard...

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.