# Ability to search strings within filter selections

**URL:** <https://community.palantir.com/t/ability-to-search-strings-within-filter-selections/1373>\
**Category:** Product Feedback\
**Tags:** ontology-management, workshop\
**Created:** [September 25, 2024, 5:20pm UTC](https://community.palantir.com/t/ability-to-search-strings-within-filter-selections/1373 "2024-09-25T17:20:27Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![WorkshopWizard](https://avatars.discourse-cdn.com/v4/letter/w/c0e974/32.png) [@WorkshopWizard](https://community.palantir.com/u/WorkshopWizard)\
**Post date:** [September 25, 2024, 5:20pm UTC](https://community.palantir.com/t/ability-to-search-strings-within-filter-selections/1373/1 "2024-09-25T17:20:27Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![OntologyOncologist](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/ontologyoncologist/32/1646_2.png) [@OntologyOncologist](https://community.palantir.com/u/OntologyOncologist)\
**Post date:** [October 2, 2024, 9:06pm UTC](https://community.palantir.com/t/ability-to-search-strings-within-filter-selections/1373/2 "2024-10-02T21:06:26Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![WorkshopWizard](https://avatars.discourse-cdn.com/v4/letter/w/c0e974/32.png) [@WorkshopWizard](https://community.palantir.com/u/WorkshopWizard)\
**Post date:** [October 4, 2024, 3:51pm UTC](https://community.palantir.com/t/ability-to-search-strings-within-filter-selections/1373/3 "2024-10-04T15:51:32Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![stefanyb](https://avatars.discourse-cdn.com/v4/letter/s/22d042/32.png) [@stefanyb](https://community.palantir.com/u/stefanyb)\
**Post date:** [October 14, 2024, 2:43pm UTC](https://community.palantir.com/t/ability-to-search-strings-within-filter-selections/1373/4 "2024-10-14T14:43:12Z")

</div>

Second our need for the feature request flagged my Mr. Wizard. Thank you

---

<div class="post-metadata">

**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\
**Post date:** [January 25, 2025, 7:30pm UTC](https://community.palantir.com/t/ability-to-search-strings-within-filter-selections/1373/5 "2025-01-25T19:30:33Z")

</div>

Automatically bumped on January 25, 2025, 7:30pm UTC



---

<div class="post-metadata">

**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\
**Post date:** [May 17, 2025, 8:22am UTC](https://community.palantir.com/t/ability-to-search-strings-within-filter-selections/1373/6 "2025-05-17T08:22:40Z")

</div>

Automatically bumped on May 17, 2025, 8:22am UTC



---

<div class="post-metadata">

**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\
**Post date:** [September 7, 2025, 11:15pm UTC](https://community.palantir.com/t/ability-to-search-strings-within-filter-selections/1373/7 "2025-09-07T23:15:25Z")

</div>

Automatically bumped on September 7, 2025, 11:15pm UTC



---

<div class="post-metadata">

**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\
**Post date:** [March 8, 2026, 10:09pm UTC](https://community.palantir.com/t/ability-to-search-strings-within-filter-selections/1373/8 "2026-03-08T22:09:31Z")

</div>

Automatically bumped on March 8, 2026, 10:09pm UTC



---

<div class="post-metadata">

**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\
**Post date:** [November 3, 2026, 4:32am UTC](https://community.palantir.com/t/ability-to-search-strings-within-filter-selections/1373/9 "2026-11-03T04:32:21Z")

</div>

Automatically bumped on November 3, 2026, 4:32am UTC


