CONTAINS Constraint not always working

[julienallard1]

Hi all,
I found that the CONTAINS constraint will work under certain circumstances only. Say I have I field “REF” with many entries with values like:
KeyFirst1_txt
KeyFirst2_txt
KeySecond1_txt
KeySecond2_txt
LockFirst1_txt

Now say I want to retrieve all the entries with “Key” in it, the CONTAINS constraint won’t work (REF contains “Key”). Neither if I want all the ones containing “Second”, the expression REF contains “Second” will found nothing.

But if I look for “KeyFirst” or “_txt” it’s gonna work. As if numbers and underscores could be used as separators but not letters.

If find it’s a bug since “KeyFirst1_txt” DO contains “Key” and the search won’t find it. (Not in a “do a search”, :filtered or even in the Data tab of the editor).

Now that I’ve been working on my app for a month, it’s a bit too late to change the way my entries are made… Will have to find a workaround

[JohnMark]

It’s kind of a bug, but it work that way. Any none letter act as a space in search mode. If you simply rename your key words, than it will work (faster work around I found ).

KeyFirst1_txt will become Key_First1_txt.

[julienallard1]

It would work, but I already have so much workflows and element referring to those entries that I prefer to keep them that way.

Lesson to remember: Camel Case nomenclature is to avoid in Bubble… Snake Case is better.

[JohnMark]

I found that Make Changes to a List of things can do the job of renaming pretty fast. Yes, we learn all kind of lessons in this adventure