@julienallard1 @BudSpaces
I tested both the auto-complete fuzzy search plugin vs the method Julien had shared.
Below are some screen shots from the debugger console showing different errors / alerts
The first are the errors reported when using the autocorrect plugin. The second is what I got using the method outlined by Julien.
This first one with auto-complete plugin on the page actually occurs even when I haven’t started a search…
This second one is from the method outlined by Julien when a search is performed.
Seems to me like Juliens’ method is clearly a winner in this situation. It seems like simply having the auto complete on the page it is causing performance issues. What I assume is that it is performing searches even before it is prompted to do so in order to populate the plugin with the data needed to “parse”.
I am doing this on a list of approximately 1700 items.
What is more, is after using the plugin method, which ironically produces no results even after waiting for 5 minutes, it also doesn’t load the entire list of items to be used in the “parse” as fast as a simple repeating group with a basic “do a search for” in the datasource.
I’m not sure exactly why this is, but I was attempting to use the autocomplete on this data type and had experienced the problems and was close to giving up on the possibility of giving my users the type of user experience I desired.
Now, thanks to Julien, I have a way to add the functionality to the app in way that actually works.
By the way, when using Juliens method, it took about 3 seconds for the repeating group to get results that match the inputs value, and it returned all that “contain” the text value in the search input.
Thanks Julien!