New behavior for "contains" vs "contains keyword(s)"

Thank you. I see

I’m using “contains” in a rg search for a text typed into a text field.

It works for a few seconds, but a second or so after the user stops typing the search results in the RG disappear. Why would this be?

I think the issue is that is case-senstive. How can I make the contains search ignore case?


Did you find a solution to this? I am facing this currently.

As a solution, you can create a new field called query where you save data in a lower case format that you would like to use for searching purposes.
query = Input First Name's value:lowercase:trimmed Input Last Name's value:lowercase:trimmed Input Phone's value:trimmed

1 Like

where is the “contains keyword(s)” thing? All I see is “contains” and “doesn’t contain”…

1 Like

Hey @allenyang, I’m wondering if this is “contains keywords(s)” intended behavior because I’m still not able to use this feature (it would make my list filter so much cleaner):

It doesn’t match with words that have any punctuation. So words at the end of a sentence, before a comma, or before a semicolon are not matched.

For example, I’m trying to do a search for text in my database. The text:

A new web app.

Wouldn’t match a search for “a new web app” because app has a period (.)

Let me know if this makes sense.

We aren’t able to repro that on our end; could you please submit a formal bug report with more details?

It works in a way I don’t understand.

I created a bug report #14883

Is it possible to add a “case-insensitive” version of the “contains” operation?


This would be so incredibly helpful. Very frustrating that currently it’s so difficult to create a decent search (and we’re not even talking sophisticated fuzzy search) when the :contains operator is case-sensitive.


Agreed. The search for text capabilities are greatly lacking without preloading all of the data client-side.

@allenyang - Is there a reason why the contains and contains keyword functions are not both case-insensitive? These were so close to allowing the flexibility that most users need, but JUST missed the mark. Any input would be helpful since doubling up the database just doesn’t make any sense.


“contains keyword” doesn’t show for me on any text type data, all i get is the standard “contains”, how do i get it to show?

bump, this feature would be so much more useful if it were case-insensitive


Yes where is it?

I can’t find it

1 Like

plus one this

I tried using both the “contains” and “contains keywords” function to match an image from my database with an audio file that the user is uploading. So that when the audio file is saved to the database it saves with the correct image.

I’ve uploaded all the image options in bubble along with keywords that the audio files has in its name.

For example, one of the audio files names is “changing beliefs and perceptions”. There are other audio files the user will be uploading with the keyword “changing”. There is also an audio file called theyll be uploading called “changing beliefs and perceptions II” which has a different image.

So I saved the image name as the following:
Datatype: audio images
field: image/img
Audio file keywords: beliefs perceptions I

I have the files names that the user is uploading displaying in a repeating group along side the image element with the following:
Search for audio images: name contains keywords: current cells files name

Its only showing the images that are an exact match instead of the contained keywords.

Can you help me understand what i need to do differently to achieve matching the files with the correct image?

Thanks in advance!

Did you ever find it? It’s not appearing for me either :sweat_smile:

I think it is an operator for text

Thank you. I think there’s some weirdness about my use case as it’s not appearing for a bit of text :frowning: Can't see "contains keywords(s)" - #6 by cohereandnow