Reputation: 9714
I'm trying to learn about bidirectional relationships involving bridge table.
I have BridgeOrders having 1:M relation with FactSales.
And 1:M relation with FactCharges.
Product Dimensions filters the FactSales.
So that the filter flows from FactSales to the BridgeOrders to FactCharges, I have enabled the bidirectional relationship between BridgeOrders and FactSales.
Now selecting a Product shows me corresponding sales and their charges.
In the same table visual or a slicer if I add ChargeName, then it seems to filter the table visual for that respective ChargeName.
So, I'm trying to understand under what situation will I need to enable the bidirectional relationship between BridgeOrders and FactCharges? What will that achieve?
Upvotes: 0
Views: 25
Reputation: 101
Based on my experience so far, there has never been any "absolute necessity" to implement bidirectional relationship.
No doubt bidirectional relationship brings convenience in certain scenarios; it might also produce side effect without be noticed. Here's a good reference to delve into details of bidiretional relationship,
Bidiretional relationship and ambiguity in DAX
Upvotes: 0