When we are using constraints in a search and the field we are going to add a constraint to is a list, that field should have more than just the contains, doesn’t contain, is empty or isn’t empty comparatives. There SHOULD be also a Contains List comparative and also a doesn’t Contains List comparative. We should not have to use Advanced Filters for this.
Please Upvote HERE if you think Bubble should update this.
Upvoted!
Much needed though from what I understand Bubble has a lot of restructuring to do to allow this.
They shouldn’t. There is already a contains list operator, but just not applied within the constraints of a do a search. Hopefully with enough upvotes they might get around to it.
Also an “Intersect with” operator will help so much in many ways.
Imagine those cases where you have a list of users with a list field and needs to perform a search in all the users where the list field has at least one of the options (or some of them) selected in a filter (also list-type).
I know that currently we can use some workarounds but would be nice to have it in as a native way.
We can do that natively currently using the filtered operator and the ‘Advanced’ Filter. But yes, if it was just in the normal constraints would be better as I do believe these types of filters are currently being applied server side anyway.
Upvoted!
It would be amazing to have that, it would really help not to have to use advanced.
