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

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

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.



Follow on LinkedIn
@ 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!:
Power BI Cookbook Third Edition (Color)

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.



Follow on LinkedIn
@ 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!:
Power BI Cookbook Third Edition (Color)

DAX is easy, CALCULATE makes DAX hard...

Helpful resources

Announcements
ArunFabCon

Microsoft Fabric Community Conference 2025

Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.

December 2024

A Year in Review - December 2024

Find out what content was popular in the Fabric community during 2024.