Forum Discussion

DouweMeer's avatar
DouweMeer
Icon for Impactful Individual rankImpactful Individual
1 year ago
Solved

Ambiguous path - Don't understand why

I have a dimension table that attempts to filter two other dimension tables which are linked to a fact table, say, customer and product. Normally, you'd just create a 1 to many cardinality between th...
Need Help
Thomaslleblanc's avatar
Thomaslleblanc
Icon for Super User rankSuper User
1 year ago

You would have to go back to the data engineer of the dimension and fact and separate thise dependency. Even tough more than one customer can sell a product, you can not have the same customer selling the same product on one sales line item. Designing the customer/product dimension would be a way, but you would need a snowflake ProductList table that can filter to one product if the customer is not included.

  • DouweMeer's avatar
    DouweMeer
    Icon for Impactful Individual rankImpactful Individual
    1 year ago

    I'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.