Adding a search box to a slicer (similar to that of a filter) would be very useful for slicers with several hundred possible selections. It would be useful if the multiselect feature could also be incorporated
We are looking at a variety of improvements for slicers in conjunction with adding slicer functionality (and improving PivotTables) for Excel on the web. Search is one of the features we’re interested in adding. Please keep the votes coming so we can properly prioritize this work.
Andrew Ashurst commented
Yes, it's a shame this isn't getting more traction. I didn't clock that PBI already has this when I looked at this thread before. Thing is we all have Excel/PQ and Power Pivot and can "publish" to our intranets or sharepoint/MS Teams directly from it. To do the same with PBI your organisation has to hand over some more dosh to MS - I guess for that extra dosh it had better have some extra features - even if, like this, I suspect the feature would be trivial for MS to add to Excel.
Just being able to type the first letter would be a great help when you have a long list.
James Duade commented
100% agree, a search option for slicers would be fantastic!
Rick Ward commented
The slicers in excel should work like the slicers in PowerBI. If I have, for example, a slicer by Customer, and have 500 Customers, it's hard to find them in Excel. In PowerBI, I can enable a search field and it filters the list down so you can select the one(s) you want
Yes, a search box for slicers would be fantastic!
Kenneth Barber commented
The multi-select feature is already available in Excel 2016. It's an extra icon beside the filter on the Slicer. Or did you mean that multiselect should be incorporated into the search somehow?
Also, if you have several hundred possible selections in a single Slicer, you could avoid some searching if you can somehow group those selections. For example, if you have a list of a few hundred countries, then in the source table, add a field for the continent and add a Slicer for that.
If your source table (Table1) has repeated countries, then you will need another table (Table2) that maps continents to a unique list of countries. Then use INDEX(Table2[Continent],MATCH([@Country],Table2[Country],0)) in the continent column of Table1 to get the continent listed in Table2.