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

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Learn more

Reply
Anonymous
Not applicable

One to One Relationship

I have a table that is not allowing me to create a 1:* relationship when it should. 

I've tried to remove duplicate, null, and blank values, and I've exported to Excel to try and highlight duplicate values, but it's still not letting me set the relationship. 

 

It's automatically creating a many to many relationship when it should be 1:*

I get this error. *The cardinality you selected in't valid for this relationship

 

any ideas?

 

 

1 ACCEPTED SOLUTION
Anonymous
Not applicable

@Anonymous  - That error indicates that the key column of the dimension (one-side) has duplicates or blanks. To troubleshoot:

  1. Make sure you're joining on the correct columns.
  2. Make sure there are no blanks in the key (join) column.
  3. Make sure there are no duplicates in the key (join) column.
I hope this helps. If it does, please Mark as a solution.
I also appreciate Kudos.

View solution in original post

4 REPLIES 4
Anonymous
Not applicable

@Anonymous  - That error indicates that the key column of the dimension (one-side) has duplicates or blanks. To troubleshoot:

  1. Make sure you're joining on the correct columns.
  2. Make sure there are no blanks in the key (join) column.
  3. Make sure there are no duplicates in the key (join) column.
I hope this helps. If it does, please Mark as a solution.
I also appreciate Kudos.
Anonymous
Not applicable

I've fixed it... I'm not exactly sure how, but I re-did the qurey and merge.

On my original join I set the criteria to filter the last report date and join w/ the other source data.

On the new one, I first copied my table then filtered to include only the Latest report, then merged on that. That worked.

Thanks.

Anonymous
Not applicable

yes, I've gone through those steps and it's still registering the column as a Many column... I have this same issue in another model that I'm working on and I'm stuck as to what to do to resolve it.

 

RobbeVL
Impactful Individual
Impactful Individual

Happy to help with your dataset...

Helpful resources

Announcements
Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

October Power BI Update Carousel

Power BI Monthly Update - October 2025

Check out the October 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors