Forum Discussion
Community ChampionIs this the normal behavior? - Puzzled by result
Hi AlB,
on the expanded version of the SalesTable (which includes the Calendar Table as you've mentioned) now you have two columns 'Date', the native one of 'Sales' plus the one coming from 'Calendar'.
Therefore on the measure:
CALCULATE(SUM(SalesTable[Amount]), ALL(SalesTable[Date]) )
the filter coming from the Slicer (on which you 're using Calendar[Date]) remains active because you're removing the filter only from the 'Date' column that is native to Sales
Community ChampionHi LivioLanzo
Thanks very much for your prompt response. I do not quite agree with what you say but it certainly put me in the right direction. Here's what I think is happening. Let me know what your take is:
I was using ALL(SalesTable[Amount]). With this we're removing the filters on that column but the other column in SalesTable, SalesTable[Amount] will still be crossfiltered by the slicer. To prevent this, we need to do the ALL( ) on the whole SalesTable. This measure works with the slicer on CalendarTable[Date] still active:
SalesMeasure3 = CALCULATE ( SUM ( SalesTable[Amount] ); ALL ( SalesTable ) )
I do not think expanded tables play a role here since the expanded table of SalesTable includes CalendarTable but the expanded table of CalendarTable does not include SalesTable.
What do you reckon?
Solution SageHi AlB,
on the expanded version of the SalesTable (which includes the Calendar Table as you've mentioned) now you have two columns 'Date', the native one of 'Sales' plus the one coming from 'Calendar'.
Therefore on the measure:
CALCULATE(SUM(SalesTable[Amount]), ALL(SalesTable[Date]) )
the filter coming from the Slicer (on which you 're using Calendar[Date]) remains active because you're removing the filter only from the 'Date' column that is native to Sales
- AlB
I see what you mean. You're right. I'll mark the post as solution when the feature works again.
Thanks