Allow 'Search' within slicer filtering for non-text attributes
Text attributes can be 'searched' within report slicers. However, integers cannot. For example, if someone wants to quickly find and slice by a Customer Id, it is very cumbersome right now - lots of scrolling. A simple search by Customer Id (as an integer) within the slicer would make it much faster and a better user experience
@Anonymous: True, and that is what we did. We just shouldn't have to do that.
Agree. As a workaround, you can duplicate the column, change type to text and use that in the slicer.