Forum Discussion
Slicer filtering another Slicer
Anonymous
This happens because you keep Areas and Subareas in two different tables. I don't think this is how it should be in this case. Please move areas and sub-areas to one table and the problem will disappear due to the auto-exists feature (which will then kick-in). Alternatively, you could create a simple measure that would check for each sub-area if there's an entry in the fact table for the currently selected area and hide the rows in the sub-area slicer which do not have any entry. But I think the best solution is to move areas and sub-areas into one table. This makes sense because there seems to be a natural hierarchy with areas and sub-areas.
Hi daxer.
I've tested that before posting, and the problem was the same. I've changed to Chiclet Slicer and now it works!
Anonymous
I can assure you that if you keep both in the same table, slicers attached to Area and Sub-Area will be cross-filtering each other without any other setup. This is, as I said, due to how auto-exists works. However, for this to work you only have to keep the combinations of (area, sub-area) that are not empty, meaning a combination must have at least one entry in the fact table. If you have empty combinations, they WILL show up. If this is the case, the only other good solution is a simple measure that will filter one of the slicers through the Filter Pane based on the selections made in the other slicer. This could, in fact, work both ways for both slicers at the same time. The solution with a filtering measure does not require keeping the combinations in one table.
Take a look at model:
https://1drv.ms/u/s!AmzyDwofiLHinFExd83TORK8CVq3?e=1BNpFI
It should work, I know that, but it's always showing those "ghost" results.
PaulDBrownCommunity Champion
Anonymous
Which "ghost results"? The way the model is set up, the slicer hierarchy works