# Glide not retaining 'keyword search' entries

**URL:** <https://community.glideapps.com/t/glide-not-retaining-keyword-search-entries/64808>\
**Category:** Report a Bug\
**Created:** [August 8, 2023, 12:18pm UTC](https://community.glideapps.com/t/glide-not-retaining-keyword-search-entries/64808 "2023-08-08T12:18:13Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Katelyn\_Alberts](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/katelyn_alberts/32/44421_2.png) [@Katelyn\_Alberts](https://community.glideapps.com/u/Katelyn_Alberts)\
**Post date:** [August 8, 2023, 12:18pm UTC](https://community.glideapps.com/t/glide-not-retaining-keyword-search-entries/64808/1 "2023-08-08T12:18:13Z")

</div>

**My App/Pages support link:**  
[https://go.glideapps.com/support/843be8ab-4fe5-4e6f-b524-d4b5d7357f82](https://go.glideapps.com/support/843be8ab-4fe5-4e6f-b524-d4b5d7357f82)

**Describe the bug:**  
Glide is not retaining keyword search entries (on search bar in details page on classic apps). Every time I’m looking for something, the keywords delete out if I click on one of the options I’m looking at. I, then, lose my place in the search because the keyword is gone, and then I have to retype it again and again and again because it keeps deleting out as I search through whatever I’m looking for.

**Expected behavior:**  
Keyword entry should remain in search bar while user is looking through options on an inline list on a details page. At least while the user is actively using the app.

**How to replicate:**  
Use the keyword search tool on any of my tabs. Search “curl” or “blonde”, anything that related to hair. If you log in as me, I have a new ‘gallery’ tab of hair pictures similar to IG. If you enter any specific interest there and then click on an option, your entry will erase as well.

**Link to demo recording (optional):**  
Search examples:

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/b/a/ba9c28bed50851d4b5e52c36da85e33f34180f86.jpeg)  
 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/5/a/5a40f47928370180422514f0644fe8aea1fe6648.jpeg)

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [August 8, 2023, 11:43pm UTC](https://community.glideapps.com/t/glide-not-retaining-keyword-search-entries/64808/2 "2023-08-08T23:43:35Z")

</div>

Yeah, I can reproduce this, I agree it’s undesirable behaviour.

I think this is still a Classic App right? I don’t know if you can submit tickets for Classic Apps anymore.

---

<div class="post-metadata">

**Author:** ![Katelyn\_Alberts](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/katelyn_alberts/32/44421_2.png) [@Katelyn\_Alberts](https://community.glideapps.com/u/Katelyn_Alberts)\
**Post date:** [August 9, 2023, 2:00am UTC](https://community.glideapps.com/t/glide-not-retaining-keyword-search-entries/64808/3 "2023-08-09T02:00:46Z")

</div>

oh man, that would really stink. Especially after having to upgrade to teams and then getting no bug support? Has mostly everyone switched to the new glide apps, I can’t imagine that it’s that easy for everyone to rebuild their entire apps from classic?

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [August 9, 2023, 2:07am UTC](https://community.glideapps.com/t/glide-not-retaining-keyword-search-entries/64808/4 "2023-08-09T02:07:59Z")

</div>

> [@Katelyn\_Alberts](#):
>
> Has mostly everyone switched to the new glide apps

As it’s going to be sunset at some point, and you can’t actually create new Classic Apps anymore, I think it might be a yes. At least we’re trying to convert as much as we can within our agency.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [August 9, 2023, 2:09am UTC](https://community.glideapps.com/t/glide-not-retaining-keyword-search-entries/64808/5 "2023-08-09T02:09:55Z")

</div>

One option you have would be to convert it to a custom search. That will give you the behaviour back that you want, but will cost you in extra updates.

---

<div class="post-metadata">

**Author:** ![Katelyn\_Alberts](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/katelyn_alberts/32/44421_2.png) [@Katelyn\_Alberts](https://community.glideapps.com/u/Katelyn_Alberts)\
**Post date:** [August 9, 2023, 12:54pm UTC](https://community.glideapps.com/t/glide-not-retaining-keyword-search-entries/64808/6 "2023-08-09T12:54:29Z")

</div>

Ya I hear you, and I eventually want to switch over to the new Glide apps too. I just feel like it’s a little soon to be cutting us off from support without all the kinks worked out on how to seamlessly switch over all of the functionality.

---

<div class="post-metadata">

**Author:** ![Katelyn\_Alberts](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/katelyn_alberts/32/44421_2.png) [@Katelyn\_Alberts](https://community.glideapps.com/u/Katelyn_Alberts)\
**Post date:** [August 9, 2023, 12:55pm UTC](https://community.glideapps.com/t/glide-not-retaining-keyword-search-entries/64808/7 "2023-08-09T12:55:56Z")

</div>

Hi Darren! Can you explain a little more about that?? How to create a custom search and what you mean about costing me?

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [August 9, 2023, 12:59pm UTC](https://community.glideapps.com/t/glide-not-retaining-keyword-search-entries/64808/8 "2023-08-09T12:59:04Z")

</div>

There are a few ways to go about it, but essentially it boils down to something like:

- Disable the search in your list component
- Add a Text entry component at the top of the screen
- Point that text entry component at a user specific column
- Use the contents of the user specific column to filter your list

The extra updates come from the fact that as a user enters text in your custom search box, it is updating the attached table in real time. So every search counts as an update.

---

<div class="post-metadata">

**Author:** ![Hassan\_Nadeem](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/hassan_nadeem/32/72956_2.png) [@Hassan\_Nadeem](https://community.glideapps.com/u/Hassan_Nadeem)\
**Post date:** [August 9, 2023, 1:01pm UTC](https://community.glideapps.com/t/glide-not-retaining-keyword-search-entries/64808/9 "2023-08-09T13:01:04Z")

</div>

> [@Darren\_Murphy](#):
>
> One option you have would be to convert it to a custom search. That will give you the behaviour back that you want, but will cost you in extra updates.

The native search column searches for all the columns/info in the detail screen correct? How would a custom search do that?

Wouldn’t it be too much work to connect all columns to one custom search bar? How would the filters work?

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [August 9, 2023, 1:04pm UTC](https://community.glideapps.com/t/glide-not-retaining-keyword-search-entries/64808/10 "2023-08-09T13:04:18Z")

</div>

It’s a custom search, so you can set it up to work any way that you like. Some ways will be easier than others, depending on the desired result.
