Calculation group using filter modifier looks like a bug

Hi again Anonymous 

I have tried to isolate the conditions required to reproduce this bug, so I created a very simple PBIX to demonstrate the issue (attached).

To reproduce this apparent bug, I believe these are the requirements:

1. Create a calculation group with a calculation item that uses ALLSELECTED (), the simplest example being:
   CALCULATE ( SELECTEDMEASURE(), ALLSELECTED () )
2. Create a a matrix with at least two fields in the Rows field well.
3. Place a measure which itself does not use ALLSELECTED in the Values field well.
4. Apply the above calculation item as a filter to the matrix visual.
5. Expand the rows of the matrix in a "ragged" fashion, so that some branches are expanded to lower levels than others.

The bug can be avoided by removing any of the above conditions, for example:

1. Expanding all branches of the matrix to the same level
2. Including a measure in the matrix that does use ALLSELECTED, even in a trivial way, such as
   Sales Modified = SUM ( Sales[Sales] ) + CALCULATE ( BLANK(), ALLSELECTED () )

Does this sound right?

I intend to raise this as an issue. Let me know if you have any other thoughts 🙂

My takeway at the moment is that it is risky to use ALLSELECTED () within calculation items.

Regards