Search widget incorrectly showing "No search results" prior to pressing Enter

[COwen]

Hello there,

I'm using the Search widget for two feature layers in an Experience Builder application. As shown below, I'm searching within 5 fields for this particular feature layer. I can get search results without pressing Enter for some of the fields but for others I get "No search results" and have to press Enter to see the results. Why might this be the case? There are differences between them (e.g. max length, whether null values are allowed) but I can't imagine it's related to these differences.

  

Also, for all of the 5 fields, I get "No search results" for text that is not at the beginning of the string and have to press Enter to see the results. Is there a way to resolve this, even if this means removing all search results before pressing Enter?

Many thanks

[RebeccaWatson1]

Many thanks Alex - that has improved the functioning of the widget greatly. Very helpful 😊

[COwen]

Hi Alex,

Thanks so much for letting us know - really useful!

Kind regards, Caitlin

[SStopyak_BruceHarris]

I've covered this topic with ESRI Support for hours (with the Query widget); documenting, making demonstration videos, screenshares, data shares...and ended up without resolution. Suggestions work fine for a single unbroken string like a parcel number but addresses don't work. I suspect this could be a query performance-driven problem because it feels like it might be more prevalent with larger datasets. The main data value pattern that is problematic is <number><space><alphanumeric> which is the case for almost any address. The only real workaround I have found is to use a "contains" search instead of suggestions for unique values. I fully disagree with the assertion that the suggestions that come up don't need to work correctly,  because they are just suggestions. That is not the expected behavior. No user is going to see it that way.

Note for ESRI Devs: I'm not a javascript developer by trade, but if the search and query are using regex expressions, maybe the expressions aren't accounting for this number space alphanumeric pattern correctly? Conversely, if it is a pure SQL expression, maybe that query formatting needs a look.