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.
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?
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
112 | |
100 | |
76 | |
64 | |
63 |
User | Count |
---|---|
142 | |
105 | |
102 | |
80 | |
67 |