Ignore Empty Constraints Not Working

[openocean.tampa]

Hello,

I am not sure if this is a bug or not but I am having issues with filtering lists. The main issue is that I am using dropdowns or multidrop elements to allow Users to select filters for the list, which works fine to my knowledge. The issue occurs when the dropdown or multiselect is empty. I have it set to ignore empty constraints, but for some reason it is not ignoring these constraints.

I have looked on the forum and found a variety of other people with this same issue in the past, but have not seen any solutions posted. Is there any known way to make this work?

Happy to post screenshots if needed.

Here are the other posts I saw about this:

Ignore empty constraints and custom states

Hi bubble friends Anyone noticed that when using custom states for filtering searches the “ignore empty constraints” option doesn’t work? I am saving search parameters in states for users browsing for produts. The sates are lists that contains brands, price range, etc. Each state is a list of a specific info. Then I have a RG of products filtered by the states, but I am getting no results unless I populate all the states, which leds me to the conclusion that empty states are blocking the resu…

Ignoring empty constraints

It doesn’t matter what I do, Bubble seems not to ignore empty constraints on input/dropdown fields when I search for data. Does anyone else have this issue?

Issue with Bubble's Multiselect Dropdown plugin & "Ignore Empty Constraints"?

Hey all, Has anyone tried to use the Multiselect Dropdown plugin as a Data Source filter for a RG? My example: -My RG lists “Plans” -Each “Plan” has certain text fields -I have created a Multiselect Dropdown listing the text options possible . My hope is the user could select the text values they want to filter on. Filter/Constraint: Field “is in” MultiSelect Dropdown’s value (Text is in multiple texts) Issue: When the Filter has one or more values, it all works as expected…but when the M…

Also, I did see this post about a new feature that was supposed to fix this, however I am still having this issue…

[New Feature] Version 7: changing how constraints work with empty lists

Hi everyone, We’re changing how “Ignore empty constraints” works when 1) the constraint type is “is in” or “isn’t in” and 2) the constraint value is an empty list. In the past, here’s how these constraints were evaluated with an empty list as the value: old “is in” “isn’t in” “Ignore empty constraints” true false true “Ignore empty constraints” false false false Here’s a table of how these constraint types will behave in the future when the value is an empty list (with changes it…

[rpetribu]

Hi @openocean.tampa

You can add a condition in the conditional tab of your repeating group to check if any filter is beeing applied by your user. If users are not filtering at all (if your dropdown or multidrop elements is empty), change the source of this repeating group (make a search with no constraints)…

[ed727]

@openocean.tampa

The issue occurs when the dropdown or multiselect is empty. I have it set to ignore empty constraints, but for some reason it is not ignoring these constraints.

Knock on wood I haven’t had an issue. Try posting a screenshot of your search setup – might be something in there that’s amiss.

[openocean.tampa]

Hey @rpetribu!

Thanks for the help, it was a little more complicated for my case… I have a total of 5 filters (sort by, 3 different forms of multidrops, and a search bar) and they are all stored in a state on the repeating group. Then the repeating group had to have 11 different conditionals to change the data source based on which of these were empty or not, but it seems to be working now haha.