Single/Multiselect filters are currently limited for users to find a value to select if it appears after a delimiter such as an underscore (“_”).
This is important as our users are used to other tools where they can type search by characters that may appear after a delimiter. Right now, any potential selections in a multiselect filter will not show up if searched using characters that come after an underscore within a filter field.
For example, if a single or multi-select filter has the following selections available:
Firstname_Lastname
Firstname_Middle_Lastname
Lastname_Firstname
Currently, if the user clicks in the filter and types a value they know exists, such as “Lastname”, only the third value above will show up due to “Lastname” appearing after the “_” in the other two values. This is causing users to think that their data is unavailable. Unfortunately, there are business processes that limit our ability to work around the issue by normalizing values with underscores to use spaces instead. I’m unsure if other delimiters/values have the same impact as underscores.
Allowing a cohesive string search within the filter fields in Workshop would be a big improvement for user adoption of the dashboards that we are building.