Forum Discussion
Impactful IndividualAmbiguous path - Don't understand why
Hi DouweMeer , Thank you for reaching out to the Microsoft Community Forum.
Instead of separate bridge tables between your red filter and Customer/Product, build a single Customer Product bridge dimension that links both Customer and Product to Fact. Then connect your red filter table to this composite dimension. This removes ambiguity and correctly represents the many-to-many relationship between Customer and Product without circular dependencies.
Model relationships in Power BI Desktop - Power BI | Microsoft Learn
Many-to-many relationships in Power BI Desktop - Power BI | Microsoft Learn
Impactful IndividualI'm that engineer. Also, in the picture, blue box on the left would be product, blue box on the right is customer. They individually filter the fact table. Thus, if you'd filter fact table form the product table, it can individually filter the fact table from the customer table.
The intent on the red table is that for a specific customer-product combination, it can provide, say, the sales value. And then for a focusses list of customer-product combinations.
Also, perhaps needed additional context, the blue tables are dimensional table for 2 ERPs at the same time. Intent to see the dollar figure for that customer-product combination from both ERP's perspectives.
Community SupportHi DouweMeer , Thank you for reaching out to the Microsoft Community Forum.
Instead of separate bridge tables between your red filter and Customer/Product, build a single Customer Product bridge dimension that links both Customer and Product to Fact. Then connect your red filter table to this composite dimension. This removes ambiguity and correctly represents the many-to-many relationship between Customer and Product without circular dependencies.
Model relationships in Power BI Desktop - Power BI | Microsoft Learn
Many-to-many relationships in Power BI Desktop - Power BI | Microsoft Learn