The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
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
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
User | Count |
---|---|
111 | |
79 | |
71 | |
48 | |
41 |
User | Count |
---|---|
139 | |
112 | |
72 | |
64 | |
62 |