# How to get your Text fields etc. INDEXED for SEARCH

**URL:** <https://community.fibery.io/t/how-to-get-your-text-fields-etc-indexed-for-search/3327>\
**Category:** Fibery Showcase\
**Tags:** search, rich-text\
**Created:** [September 21, 2022, 6:46pm UTC](https://community.fibery.io/t/how-to-get-your-text-fields-etc-indexed-for-search/3327 "2022-09-21T18:46:25Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [September 21, 2022, 6:46pm UTC](https://community.fibery.io/t/how-to-get-your-text-fields-etc-indexed-for-search/3327/1 "2022-09-21T18:46:25Z")

</div>

Currently Fibery only indexes entity Name fields and Rich Text fields for Search.

If you also want other fields indexed, you can make your entity Name a Formula field, and stuff in all the other entity field values you want searchable.

The disadvantage to that approach is you end up with [long, complicated entity names](https://community.fibery.io/t/table-view-quick-search/1846/13).

**Here’s an alternative:**

**1) Create a Rich Text field** to contain all the text that you want indexed - I call mine “Indexable”.

**2) Create a Formula field** to collect all your other (non RTF) indexable entity fields - I call mine “Indexable Text” –

![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/b/beb286c774c7ba3274cc41070e0379a37fa04e0b.png)

_Note that you can include Single Select fields, like_ `[Task Type].Name`  
_Also, no need to include the entity `Name`, since that is already indexed._

**3) Create a Rule** that triggers when “Indexable Text” is updated, and writes it to the “Indexable” RTF field:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/113ebec9c1f106bc16afb045985b666922b0ebe3.png)

**4) Hide** the new `Indexable` and `Indexable Text` ancillary fields.

That’s All! 😃

---

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [September 21, 2022, 6:48pm UTC](https://community.fibery.io/t/how-to-get-your-text-fields-etc-indexed-for-search/3327/2 "2022-09-21T18:48:20Z")

</div>

Note that only words of 5+ characters get indexed 😢

**UPDATE: So that was very poorly worded - what I meant was that I must type at least 5 characters into Search before it returns any hits for a longer word (like “indexable”).**

Also, you can do this with just the “Indexable” RTF and a Rule (without the “Indexable Text” Formula field), but then your Rule has to trigger on updates to any of the component fields, and they also have to all be included in the RTF Template - like this:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/c/c460204a59031a502f24b893733318039c2dfc9a.png)

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [September 21, 2022, 7:55pm UTC](https://community.fibery.io/t/how-to-get-your-text-fields-etc-indexed-for-search/3327/3 "2022-09-21T19:55:28Z")

</div>

> [@Matt\_Blais](#):
>
> Note that only words of 5+ characters get indexed

🧐

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/7212346e0e28ea552cbbdc8243d7f50f9ccdda4f.png)

---

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [September 22, 2022, 3:29am UTC](https://community.fibery.io/t/how-to-get-your-text-fields-etc-indexed-for-search/3327/4 "2022-09-22T03:29:44Z")

</div>

I don’t know… but when I type “inde” into search, I get no results, even though “index” gets me what I expect - e.g. hits for “indexable”.

Maybe “all” words are indexed, but words of 5+ letters seem to need at least five letters typed in to return any hits?? In a RTF anyway.

---

<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:** [September 22, 2022, 5:34am UTC](https://community.fibery.io/t/how-to-get-your-text-fields-etc-indexed-for-search/3327/5 "2022-09-22T05:34:44Z")

</div>

There is definitely _something_ odd about how the matching works for partial words. I ran into this recently myself. If I can remember what I did and reproduce I’ll post details.

---

<div class="post-metadata">

**Author:** ![JoelH](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/joelh/32/5193_2.png) [@JoelH](https://community.fibery.io/u/JoelH)\
**Post date:** [November 7, 2022, 3:42am UTC](https://community.fibery.io/t/how-to-get-your-text-fields-etc-indexed-for-search/3327/6 "2022-11-07T03:42:24Z")

</div>

Thank you @Matt_Blais this was very helpful to me! Your index solution solved my issue neatly.

I’d clarify (for other readers) that a benefit of formatting the description with field names, is you can use it to increase readability in the search results preview. Naturally this is subject to change if Fibery modify how their search works, but as I’m writing this, it works neatly.

In my case I preferred a formula, and by prefixing some fields, the search results are easy to digest:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/1f2ec05336d27d1d885ce7255846e47a635eac33.png)
