I have a problem using the fantastic Fuzzy search from @ZeroqodeSupport and was hoping for a bit of help.
When my page loads I have arepeating group that is populated with users of a specific role and where in the database I have marked them as active.
I have a search field which is connected with the zqfuzzysearch component that when typed into changes the RG’s content to match whatever was typed in and of course retains the role and active status needed and this works fine.
I have a toggle switch that allows the user to change the contents of the RG so they can now see the ‘inactive’ users for the specific role set instead. This works fine and when the toggle is selected I reset zqfuzzysearch using their reset method.
However, when I now type into the search field nothing happens - I was expecting to be able to now search for records from the inactive users. It seems to never fire zqfuzzysearch a second time and I can’t figure out why.
When I hit the toggle again and go back to active users zqfuzzysearch is no longer fltering the view of the RG.
Please first confirm that: The data source is indeed a list (not a single item). All necessary conditions are met as outlined in our documentation.
If everything is set up correctly, try the following approach:
Step 1: Update the Fuzzy Search’s data source dynamically to match the new repeating group content. Step 2:Reset the fuzzy search input. Step 3: Display the updated list in the repeating group.
Tip: If the search is still not triggering after the reset, try adding a short delay (e.g., 0.2s) before resetting the fuzzy search input. This ensures Bubble processes the data update first.
Let me know if this helps or if you need further clarification!
Thanks @ZeroqodeSupport but nothing I do appears to fire the search for a second time. It all works fine until I hit the toggle to change the view. The initial data source for Fuzzy is set to All Active Users and when I hit the toggle I have set a condition on Fuzzy to show only Inactive Users. I then pick up the fact the toggles value has changed, reset the Fuzzy (after a 1 second delay) and then display the appropriate list in the repeating group. It all works fine until I hit the toggle. Is there a way I could share it with you for you to take a look?
Your setup sounds well-structured, and the issue likely comes down to how Bubble handles dynamic data updates with the Fuzzy Search plugin. Here are a few things to check:
Refreshing the Data Source – Fuzzy Search works with the data set it loads initially. When switching between active/inactive users, try clearing the data source before setting a new one.
Resetting the Plugin – Instead of just resetting, introduce a brief delay before updating the data source. This ensures the new list is fully registered.
Confirming the Search Triggers Again – Check if the plugin is detecting the new data by displaying Fuzzy Search’s List:count in a text element.
Using a Custom State as an Intermediary – Temporarily setting the data source to an empty list before updating it with the new set can sometimes help force a refresh.
If you’d like us to take a closer look, feel free to share a Loom video of your setup at support@zeroqode.com, and we’ll be happy to review it!
Thanks - what I have proven, following your advice, is that FuzzySearch is firing BUT the repeating group content is not getting refreshed. I have tried various things to clear the list etc but no matter what I try I can’t get the list to refresh in response to FuzzySearch once I have hit the Toggle button. I can see that the Fuzzy count changes each time but the RG doesn’t change. I may get time to add a Loom video and will do so if I can. Thanks
It sounds like Fuzzy Search is firing correctly, but the issue lies with the repeating group not refreshing, even though the data source is changing. This could be related to how Bubble handles dynamic data updates and how the repeating group is set up.
Here are a few general tips to help with this type of issue:
Ensure the Repeating Group’s Data Source is Properly Set: When you change the data, make sure the repeating group’s data source is updated properly. You can try using a “Do a Search” action after updating the custom state or data to force the RG to reload.
Trigger a Workflow to Refresh the Repeating Group: Sometimes you need a specific workflow to trigger the RG to refresh after the toggle. You might want to manually trigger a “Display List” or reset the RG’s data through a workflow.
Recheck Conditions for Visibility: Make sure that the repeating group and its content are visible and not hidden by any conditionals that might prevent the refresh.
If you’re still having trouble, I recommend checking out these Bubble resources to deepen your understanding:
I am having the same issues. I have used Fuzzy Search many times, but now, for some reason, when linking a fuzzy search with a repeating group, the only way to show the “Searched” results is by running a workflow “Display a List in the repeating group” data.
At the moment, I have added a button for the user to click. Listening for a change in the input box is no good, as this will not work until the user clicks out of the input box. If a user doesn’t click out of the input box, they will just think it’s not working. Maybe an update in Bubble has caused this problem.
Since the issue is that the repeating group is not refreshing automatically, but Fuzzy Search is still working, it likely means Bubble is not detecting the data change properly. Here are a few ways to fix it:
1. Force the Repeating Group to Detect Data Changes
Try setting the repeating group’s data source to: FuzzySearch A’s Matches:filtered (constraint: always true)
This small filter forces Bubble to recognize that the list has changed and refresh the repeating group.
2. Use a Custom State as an Intermediary
Instead of directly setting the repeating group’s data source to FuzzySearch A’s Matches, do this:
Create a custom state (e.g., searchResults) of the same data type as your list.
Set up a workflow:
When input value changes → Set custom state searchResults = FuzzySearch A’s Matches
Set the repeating group’s data source to searchResults.
This forces Bubble to update the repeating group when the input changes.
3. Manually Trigger Repeating Group Refresh
If needed, you can add a workflow:
When input’s value changes → Display List in Repeating Group (FuzzySearch A’s Matches)
This is similar to your button workaround but removes the need for a manual click.
I have tried everything to get this working and I just can’t. It is absolutely fine until I hit the toggle then I just can’t get Fuzzy to filter the RG. I have had to remove the functionality for now.
Like Shane I can only get it to filter the group by putting a button on the page, typing the data to filter by into the input box and then clicking the button. I also put an input box on the page so I can see FuzzySearch Matches Count when I type into the search field. So Fuzzy Search is filtering the data and putting it into its matches BUT the refresh of the RG never happens at any time other than the first time or when the button is clicked. I couldn’t actually get it to fire from a change to the input value.
So frustrating as it is so close to working, so the way I have left it for now if I type in the input box and then click outside of the input it will sense the change and then I can set the source on the RG to the Fuzzy matches. Is this more likely to be a bug in Fuzzy Search?
Thanks for your patience and for sharing your findings.
Based on everything you’ve described, it’s clear that:
Fuzzy Search is correctly filtering the dataset, and the match count updates as expected.
The repeating group (RG) is not refreshing dynamically after the search input changes unless you manually trigger an event (like clicking a button or clicking outside the input).
The issue might be related to how Bubble updates RG data sources dynamically rather than the plugin itself.
Possible Causes & Workarounds
1. Ensure RG Data Source Is Set to Fuzzy Search’s Matches List
The repeating group should have its data source set as:
FuzzySearch A’s Matches
instead of relying on another data structure that isn’t updating dynamically.
If your RG is using a Do a Search for Users, it may not be listening to FuzzySearch’s real-time updates.
2. Use a Workflow to Force RG to Refresh
Since the RG isn’t detecting the updates dynamically, try the following approach:
Add a workflow event: “When Input’s Value is Changed”
Inside this event, use “Display List” in Repeating Group → set the list to FuzzySearch A’s Matches.
If that doesn’t work, try clearing the RG’s list temporarily before setting it again (e.g., set the source to an empty list, wait 0.1s, then set it to FuzzySearch A’s Matches).
3. Ensure the Input Change Is Being Detected Correctly
Some users have reported that Bubble does not always detect real-time input changes well when they are used to filter RGs.
A workaround is to add a button that explicitly triggers “Display List” in RG after a search input update.
Alternatively, try using a Custom State:
When the input changes, store the value in a custom state.
Set RG’s data source to FuzzySearch A’s Matches:filtered by Custom State.
The data source is indeed a list (not a single item).
Tip: If the search is still not triggering after the reset, try adding a short delay (e.g., 0.2s) before resetting the fuzzy search input. This ensures Bubble processes the data update first.
