My team inherited a pivot that does this.
Workbook uses multiple SQL statements to populate multiple pivots on multiple tabs.
The pivots are linked using slicercache. The "controlling" pivot has a larger list than the destination pivot.
On the original/unmodified workbook, when the "controlling" pivot chooses only items that are not in the destination pivot, when the last item is sliced out, the pivot displays "multiple items" selected and no data appears in the pivot.
On the changed version, when the last item in the destination pivot is removed, it reverts to "all".
Any ideas on forcing this behavior or what's likely to be the setting that allows for it?
I believe the only change to the destination pivot is in the SQL statement.
Slicercache is being managed like this if it is relevant.
And i always go with, don't alter what works unless it's horribly innefficient or broken.
Mike
Workbook uses multiple SQL statements to populate multiple pivots on multiple tabs.
The pivots are linked using slicercache. The "controlling" pivot has a larger list than the destination pivot.
On the original/unmodified workbook, when the "controlling" pivot chooses only items that are not in the destination pivot, when the last item is sliced out, the pivot displays "multiple items" selected and no data appears in the pivot.
On the changed version, when the last item in the destination pivot is removed, it reverts to "all".
Any ideas on forcing this behavior or what's likely to be the setting that allows for it?
I believe the only change to the destination pivot is in the SQL statement.
Slicercache is being managed like this if it is relevant.
Code:
For Each si1 In sc5.SlicerItems
sc6.SlicerItems(si1.Name).Selected = si1.Selected
sc12.SlicerItems(si1.Name).Selected = si1.Selected
sc13.SlicerItems(si1.Name).Selected = si1.Selected
Next si1And i always go with, don't alter what works unless it's horribly innefficient or broken.
Mike
