Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
My database has products which are produced in more than one Origin (ex.: Europa, LA, Canada, etc...). At the same time, my facts data tables (Sales, Purchase, Budget) also have the same column Origin on it. My product table can have only one row by sku and my origin table have one local for each Origin.
When I connect the table Product with the table Origin (linked by Origin) and the table Product with the tables Facts (linked by sku), I can not connect the table Origin with the tables Facts, because it generates a circular condition. And if I can't connect both tables Origin and Products with the Facts table, I face filter problems issues. It doesn't filter correctly the Origin volumes or I can't filter the infos for one single sku.
The results expected are: when filtered an Origin, it shows all the skus and volumes regarding this location; when filtered a sku, all the facts (locations and volumes) related to this sku should be shown. The difficulty is, some skus have more than only one origin and I need to connect through the sku the dMaterial table with the facts tables, so it is not possible to have duplicate sku rows in dMaterial. Also, when I filter an origin, the skus regarding this location are filtered and consequently the fact tables are filtered, but some of these skus have more than one origin, so actually the volumes of this location are not indeed filtered, it was filtered a sku and several locations related to it.
If I cancel the connection between Materials and Origin to maintain only between Origin and Facts table, when filtered an origin, it wouldn't filter the skus.
@MateusStefani wrote:My database has products which are produced in more than one Origin (ex.: Europa, LA, Canada, etc...). At the same time, my facts data tables (Sales, Purchase, Budget) also have the same column Origin on it. My product table can have only one row by sku and my origin table have one local for each Origin.
When I connect the table Product with the table Origin (linked by Origin) and the table Product with the tables Facts (linked by sku), I can not connect the table Origin with the tables Facts, because it generates a circular condition. And if I can't connect both tables Origin and Products with the Facts table, I face filter problems issues. It doesn't filter correctly the Origin volumes or I can't filter the infos for one single sku.
Hi,
Share some data and show the expected result.
My database has products which are produced in more than one Origin (ex.: Europa, LA, Canada, etc...). At the same time, my facts data tables (Sales, Purchase, Budget) also have the same column Origin on it. My product table can have only one row by sku and my origin table have one local for each Origin.
When I connect the table Product with the table Origin (linked by Origin) and the table Product with the tables Facts (linked by sku), I can not connect the table Origin with the tables Facts, because it generates a circular condition. And if I can't connect both tables Origin and Products with the Facts table, I face filter problems issues. It doesn't filter correctly the Origin volumes or I can't filter the infos for one single sku.
I have included a photo in this topic.
Check out the September 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.
User | Count |
---|---|
114 | |
88 | |
87 | |
35 | |
35 |
User | Count |
---|---|
154 | |
100 | |
83 | |
63 | |
54 |