Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
Hello community
Long time listener, first time caller.
I am new to Data Modeling in Power BI and I have this situation that I am trying to resolve for some weeks now. I have a FACT table with products (every row is a product transaction) that I need to build a relationship to the products manufactors. But the caveat in my scenario is that every product can have one or many manufactors. Here is a brief view of these 2 tables
How can I resolve this dilemma and avoid a many to many relationship structure? Should I build a table in the middle with a distinct list of product_ids and connect one to many to both sides? For me this seems like cheating 🙂
Anyway, if someone can give me some light here I will be very grateful.
Thanks
Rodri
Solved! Go to Solution.
Hi @calloni ,
Yes, a bridge table is what you require to eliminate many-to-many relationship.
Just 1 additional observation, ideally there should be only one product ID assigned against a product. In your data screenshot, Product ID 1, 2, 3 have 3 each. Maybe this is only a dummy data but just wanted to point it out.
Give a Thumbs Up if this post helped you in any way and Mark This Post as Solution if it solved your query !!! Proud To Be a Super User !!! |
Thanks for your help Anand! I really appreaciate your time!
Maybe I didn't explain myself well. The right side table is not a table of product_ids, it is a table of manufactors for the product_ids. That'ts why I have several manufactors for a single product_id (and yes this is only a dummy data for my real case scenario)
Of course I can create a table with only a distinct list of product IDs, but my question here: isn't this the same as many to many? I mean, I will have a one to many to the FACT table and a one to many to PRODUCT MANURACTOR like the following diagram:
User | Count |
---|---|
84 | |
77 | |
64 | |
51 | |
46 |
User | Count |
---|---|
101 | |
43 | |
39 | |
39 | |
36 |