I am trying to use this in a reusable element with a focus group and it doesn’t seem to work, The reusable element is used in multiple popups on one page which I think may be the problem, is there any work around to get this to work as it should?
Hello @dpaget21,
Thank you for your message!
To help us better understand this unexpected behavior you’re experiencing, could you please provide a video recording using a tool like Loom, demonstrating your setup? Please ensure you include the settings of the Input elements, the Search & Autocorrect elements settings, and the settings for reusable elements. Feel free to share any additional settings you think are necessary for us to know.
Please keep in mind that if you have multiple reusable elements or popups, it’s essential to ensure that the IDs linking the input elements and the plugin elements are unique to avoid any interference.
We will do our best to resolve this issue 
Cheers 
Hello @dpaget21,
Thank you for sending over the video. I just wanted to let you know that we have received it.
I’ll be sure to follow up with you as soon as I have additional information to provide. I apologize for any delay in communication.
Cheers
Hello @dpaget21,
I’ve come across a similar issue with another user that seems to mirror yours.
The problem arises due to the static IDs in the “Search&Autocorrect” element and the Input element. Without refreshing the page to reset the fuzzy search after its initial use, the element retains the data from its previous session.
The solution that worked involved assigning a unique string to the IDs each time the focus group or popup is activated. This can be achieved by setting up a custom state filled with a Random String using the “calculate formula” option. An example of this setup can be viewed [by clicking here]. Additionally, adding the “reset input” action from the plugin after and before closing the popups might help clear previous searches.
Please try implementing these suggestions on your end, and let us know if you need assistance with the setup or if the problem persists.
Cheers
Hello @dorel,
Would it possible to share the link of the example again?
It seems I have the same issue and I would like to set up the custom state as suggested to see if it solves my problem.
Thanks for your help
Hi @lunomis,
Thanks so much for reaching out to me
Sad to share that the page linked above has been deleted, and I can’t recreate its exact setup!
For more details, try adding a “Set State” action in a workflow that triggers when the reusable element containing the search is opened. For the ID attribute of the input and inside the plugin element, add the custom state as the dynamic expression!
Here’s an example of what the action and workflow might look like (screenshot). You can see how the plugin element is set up and how the input ID is inserted.
If you have any other questions or need further assistance, please don’t hesitate to reach out to me
Best regards 
1 Like
Hey @lunomis,
Glad to hear that my suggestion was helpful and it fixed the noticed behaviors on your side! It is my pleasure to be of assistance
If you’re enjoying our plugin and have some time, I’d greatly appreciate it if you could rate it. Simply head to the Plugins tab in the Bubble editor, search for the plugin by name, and award it the stars you believe it deserves!
Additionally, if you’d like to share your complete experience with Zeroqode, we’d be honored if you could leave your feedback at: Review.
Here are some direct links for your convenience:
- https://www.g2.com/products/zeroqode/reviews
- https://clutch.co/profile/zeroqode#reviews
- Zeroqode Reviews | Read Customer Service Reviews of zeroqode.com
Your feedback is incredibly valuable to both us and the Bubble community, inspiring us to continue delivering exceptional products and excellent service 
Feel free to reach out to us here on the forum or at support@zeroqode.com if you have any questions or encounter any difficulties!
Best regards 