Martin K. on 12 Feb 2024 14:37:42
I see a bunch of ideas submitted regarding the neglected slicer search field, from 2016 and onwards.
Microsoft, please search them out an merge them, in order to have a correct picture of the collected need for change.
The current unfinished search function in slicers such as "search for the entered search value anywhere in the field" makes it impossible to list fields "starts with" principle.
If I write ABC in the search field, I would expect exact hits for ABC, and if I write ABC*, I would expect search hits beginning with ABC, *ABC* would mean I want hits where the field contains ABC anywhere in the field, etc. (Microsoft, you have standards for this).
Please.
- Comments (2)
RE: Slicer Search refinement
Thanks for the tip on the Jeff Weir Twitter tag! I will definitely have a look at it.
RE: Slicer Search refinement
I would counter that the standard for "starts with" is ^ABC (regex syntax...). On the other hand, my users would just expect "match anywhere" as default.On collecting requirements, Jeff Weir made a post on Twitter a while back (look under #PBICoreVisuals) which had a lot of feedback on slicers, including a proposal for much better search. The hashtag is picked up by the visuals team, so it has been seen. If you want collated items noted, your best bet is to write them up somewhere covering why you need each item, then post them under that tag.