# Filter search results based on Field Values

**URL:** <https://community.fibery.io/t/filter-search-results-based-on-field-values/1052>\
**Category:** Ideas & Features\
**Tags:** search\
**Created:** [October 7, 2020, 8:24pm UTC](https://community.fibery.io/t/filter-search-results-based-on-field-values/1052 "2020-10-07T20:24:10Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [January 27, 2022, 5:39pm UTC](https://community.fibery.io/t/filter-search-results-based-on-field-values/1052/27 "2022-01-27T17:39:43Z")

</div>

> [@B\_Sp](#):
>
> I think adding the more complex filters to search would be much less useful now than indexing more content.

Can’t really agree there. I already find searching turns up more semi-related things than I would like (they’re related in a technical sense, they have the right word[s], but in the wrong place). Adding in comment indexing would _significantly_ exacerbate that without a way to turn it off.

I’m now working with a team who will be importing nearly 40,000 records all into a single database, so filtering by DB does not help narrow that down. Being able to specify what fields are being searched would be very helpful in this kind of situation and as mentioned it would also go some way to addressing your other request: [Seeing “Closed” Entities grayed out in Search Dialog](https://community.fibery.io/t/seeing-closed-entities-grayed-out-in-search-dialog/1298)

But I recognize that your particular workflow really would benefit from comments indexing. I guess my teams just don’t work as much that way, which is interesting. Or maybe it’s the _type_ of work being done. 🤔

---

_[View the full topic](https://community.fibery.io/t/filter-search-results-based-on-field-values/1052)._