This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreGet Fabric Certified for FREE during AI Skills Fest. This week only. Secure your voucher now.
I have two tables and I want to compare values between the two. The two tables both have a COUNTROWS() measure, and a City column (I basically want to measure rows per city) --- N.B The tables also have other columns such as user_id, longitude and latitude etc.
The tables both look like this:
For some reason, when I try and make a relationship between the two, it forces a many-to-many relationship. To circumvent this problem, I have introduced a new custom table with City Names, which only has distinct entries. It looks like this:
In the picture below, I want to make a relationship between the left table[By] and the middle table [Bynavn], AND between the right table[city] and the middle table [Bynavn], in order to get a common denominator.
However, when I make the relations stated above I get a forced many-to-many relationship for both tables, and I am trying to figure out why.
[Both tables are connected to a 'Date' table, if that matters].
Hi @MichaelBN
You can refer to the similar solved post for help:
https://community.powerbi.com/t5/Desktop/Forced-to-use-many-to-many-relationship/td-p/681147
https://community.powerbi.com/t5/Desktop/Forced-into-many-to-many-relationship/td-p/486504
Hi @MichaelBN
Is it possible you have multiple Nulls in the bridging table?
if so, filter these out in the query editor and retry creating the relationship 🙂
Thanks,
George
Hi @judspud
I don't seem to have any null values in either of the three tables. Any other idea about what might be causing this issue?
/Michael
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
| User | Count |
|---|---|
| 23 | |
| 21 | |
| 20 | |
| 20 | |
| 15 |
| User | Count |
|---|---|
| 58 | |
| 55 | |
| 42 | |
| 26 | |
| 24 |