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.
3 Likes
Mr Wizard,
You are correct that this isn’t the current functionality with the Single/Multi-select filters, but there way be a work-around.
Depending on your workshop setup/ usage, you could potentially break it into two steps/widgets to make this work.
Step 1 is the use the Filter list keyword search. I believe this will search for all substring within your field & will ignore the ‘_’ cutoff.
Take the filtered list from the above, then have that back the single/multi-select dropdown, & the fields you’re looking for should be present.
Hope that helps!
Thanks for your response. If I understand correctly, we would have a keyword search and a multiselect for the same property, and then just use the keyword to filter down to the right group to be available on the multiselect drop down.
While this does function, it unfortunately will not work well for our existing use-case because we would have to split multiple property fields. which will end up creating a large filter section, and requiring training many new users. We may choose to do it for some choice fields, but hopefully the ability to search beyond underscores can be included in a future release.
Second our need for the feature request flagged my Mr. Wizard. Thank you
1 Like