Bug in ArcGIS online layer search with single digit numbers in text strings workaround?

Question

I have a text string in a layer for subdivision lots that is populated as "Lot [number], [Subdivision Name]", for example "Lot 32, Osburn's Subdivision", the purpose being of course to search for various subdivision lots.  It works fine when there are multiple digits, such as 11, 32, 40, etc. but for some reason it won't provide results for searches for lots 1-9.  I even have a secondary field with a plat code text string [Unit ID]-[Plat ID]-[Lot], for example "AD0-425-25" that also won't provide results for any single digit lots.  Is there any known workaround for this besides inserting preceding zeros (Lot 05, Sunset Beach, I set this specific plat up as a test case) in both the search field and the search criteria?

Thank You

https://lenawee.maps.arcgis.com/apps/instant/basic/index.html?appid=e24fea2d21a343d69a8a5c6c0c96a6af

GISAdministratorFranklin · Answer

I recently asked the Esri AI Chatbot (in Support app) about the single-character string search problem. It's answer was that the search "doesn't recognize incomplete or single characters as valid search terms." Not sure where the AI sources that but it was an interesting response.

GISAdministratorFranklin · Answer

I have seen this same searching issue with single characters in a text field. I'll be curious to see if this is confirmed to be a bug. In my case it happens across all Esri apps I use (Web App, Experience, Instant) and the searching layer is hosted in ArcGIS Online. I can't say if the problem also happens with an Enterprise-sourced layer.

There are only 2 workarounds I know of. Unfortunately I don't think either of these will work for you:

1) Tell the users to include other parts of the intended search result. In your case I don't think that will work given your lot strings. In my case the problem is a direction letter abbreviation in between address number and street (entering "3805 s casper" does NOT produce results, "3805 casper" does). So I have been able to live with the issue for now...

2) The problem seems to be created when you set up a full text index on the AGOL hosted feature layer. I have found that if you delete the full text index, now the search will work assuming the user enters the exact string. They will even be prompted with the candidate suggestions. This might work for you with the lot field. However, by eliminating the index you loose the enhanced searching. Also, when you configure a new search in the Esri apps (ExB, Instant) a new full text index will be created automatically by AGOL when one does not exist on the layer field.