Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Hello!
Why does the original table has a one-to-many relationship with another table, but the copy of the original table has many-to-many relationship with the other table with the same columns used for connection?
With regards,
Rihards
Solved! Go to Solution.
Thank you, @amitchandak , for the quick reply!
It is not allowed to force 1-M in this case.
Banku grupēšana kopija 2 = ALL('Banku grupēšana')
Found the issue. DAX formula copies the table but adds a blank row as the last one.
Work-around for that is to use "Reference" (right-click on the table) in PowerQuery (didn't try anything in DAX)
Without the last row as blank it is possible to create 1-M relationship.
Thank you, @amitchandak , for the quick reply!
It is not allowed to force 1-M in this case.
Banku grupēšana kopija 2 = ALL('Banku grupēšana')
Found the issue. DAX formula copies the table but adds a blank row as the last one.
Work-around for that is to use "Reference" (right-click on the table) in PowerQuery (didn't try anything in DAX)
Without the last row as blank it is possible to create 1-M relationship.
@rihard505 , Force it to 1-M. Also, check there is no blank value on one side of the table. Also, The 1- M is inactive. is it working as 1-M as of now?
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!