15

Hi @dunnydf,

Thanks for your patience and for sharing your findings.

Based on everything you’ve described, it’s clear that:

  1. Fuzzy Search is correctly filtering the dataset, and the match count updates as expected.
  2. 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).
  3. 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.

Let us know how it goes! :pray:

Best Regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3