Bidirectional relationship and page level filter causing weird visual behaviour

[csaba09]

Hi All!

I have a data model which causes unexpected (to me) behaviour in the visuals. My model has some 'bad' design elements but this question is not about how to fix the model, but rather about WHY we witness the behaviour explained below.

The model has 4 tables: a dim_product dimension table, a dim_month dimension table, an actuals fact table and a plan fact table.

actuals:

plan:

dim_product dimension:

dim_month dimension:

An unusual feature is that the product column has a 'self-contained' row for product 'ab', belonging to product group 'ab'. This way, the product column can and does filter both the actuals and the plan tables.

Another unusual feature is that the plan table has a bidirectional relationship with the dim_month table.

Then, about the behaviour... In the below table visual I get what I expect: all products shown with their relevant [Actual outcome] and [Plan].

However, as soon as I set a page filter on the plan_version column to be v1, products a and b from my table visual disappear, and yet the Total row of the [Actual outcome] is still calculated correctly.

So it looks like product a and b are not available in the visual from breakdown, but in the Total they are still there. How can this happen? Why are a and b not available in the visual anymore? The action of filtering plan_version should not matter because the plan_version of v1 is the only version so it should still cover the full plan table, and also, the plan table does not filter dim_product, so dim_product should still offer products a and b in the visual.

As soon as I either change the bidirectional relationship between dim_month and plan to unidirectional, or if I just don't filter on plan_version = v1 in the page level filter, then I'll get back my expected behaviour in the visual where products a and b are both shown.

Link to pbix file: LINK 

If anyone could explain this behaviour, that would be much appreciated! Again, I'm not asking for tips on the model (I know how to fix it), this is rather a question on why this behaviour is there, given this model. Thanks!

Csaba