[Performance/WU] Multiselect Dropdown triggers full DB download on value change (Ghost Query?)

[colomina.simon]

Hello Bubblers,

I am facing a critical WU consumption issue related to the Multiselect Dropdown plugin and the “Ignore empty constraints” feature.

The Setup:

• I have a Repeating Group displaying a list of Clients.

• Pagination: displaying 10 items per page

• Data Source: Search for Clients.

• Constraints:

  1. Type = “Client” (Static constraint).

  2. Owner is in MultiselectDropdown's value (Checked: Ignore empty constraints). (I have about 8 similar dropdown filters).

The Issue: Everything works fine on page load (pagination is respected, payload is small). However, as soon as I add or remove a value in the Multiselect Dropdown (e.g., selecting a second owner).

What I observe in the Debugger/Network: It seems that for a split second during the value change, the plugin sends an “empty” or “null” state before sending the new list of values. Because “Ignore empty constraints” is checked:

1. The plugin flickers to empty.

2. Bubble drops the Owner constraint.

3. Bubble seems to trigger a “Select All” query, downloading hundreds of records (even those not matching the Type=Client (such as “Prospect” constraint sometimes appear in the raw response, which is weird).

Here is a video about what’s happening in the console

The Consequence: My WU consumption is exploding because every single click on a filter triggers a full download of the database in the background before filtering it again.

The Question: Since I have 8 different dropdowns, I cannot use the “Conditional” workaround (changing the Data Source when input is empty) for every possible combination.

• Has anyone experienced this “flickering” behavior with the Multiselect Dropdown?

• Is there a way to “Debounce” the Repeating Group search natively?

• Should I switch to a custom workflow-based state for filtering instead of direct binding?

Thanks for your help!

[boston85719]

@colomina.simon

Has anyone experienced this “flickering” behavior with the Multiselect Dropdown?

Not specifically, but I am trying to debug an issue with WUs for a search that uses the ‘ignore empty constraints’ and a constraint set for the current data time or a date time picker value. I know plugins need the element on page initialized before a plugin update function runs, and those run based on field values of the plugin, so my thought is that the repeating group is running the search without the date constraints and then runs again once the plugin date picker has run its update function.

I’d imagine there is a chance the multiselect behavior is similar, and unfortunately, I’m needing to investigate this to determine if I have to not use the ‘ignore empty constraints’.

[colomina.simon]

@boston85719

Not specifically, but I am trying to debug an issue with WUs for a search that uses the ‘ignore empty constraints’ and a constraint set for the current data time or a date time picker value. I know plugins need the element on page initialized before a plugin update function runs, and those run based on field values of the plugin, so my thought is that the repeating group is running the search without the date constraints and then runs again once the plugin date picker has run its update function.

I’d imagine there is a chance the multiselect behavior is similar, and unfortunately, I’m needing to investigate this to determine if I have to not use the ‘ignore empty constraints’.

I just tried it with a date picker and the problem is exactly the same.

I think you’re right. I’m a little surprised that I can’t find any other threads on this topic, because it can represent a huge consumption of WU.

Do you already find a workaround or not yet?
I was thinking about storing the values in CS through a “search button” or through multiple “an input’s value is change” events and based the constraints on these CS.