Forum Discussion
bypass a slicer
- 7 years ago
You may try the measure below.
Measure = VAR c = SELECTEDVALUE ( 'Table2'[cycle] ) VAR m = CALCULATE ( MAX ( Table1[month] ), ALLSELECTED ( Table1[month] ) ) RETURN SUMX ( FILTER ( Table1, SWITCH ( c, "Quick", ( Table1[cycle] = "Final" && Table1[month] < m ) || ( Table1[cycle] = c && Table1[month] = m ), Table1[cycle] IN VALUES ( Table2[cycle] ) ) ), Table1[amount] )
Go to the query editor ==> Transform ==> Pivot column.
Pivot your cycle column, splitting the single attribute values into two columns, effectivley doubling the length of your table. Then create two tables with the different columns. Also when you have the slicer slected you can go to format and "Edit Interactions". There you can set which visual will be affected by the currently selected slicer.
BR,
Chris
Hi Anonymous
thanks for you're answer.
but this is not a realistic solution when you have billions of records and not just 2 cycles
i've simplified the problem in order to make it more understandable.
and about "Edit interactions", i DO want the slicer to effect on ths outcome, but not in the usual way.
Thanks anyway :)