searching adresses requires the whole, exact phrase
Hi
for a few weeks i have a problem in my application that was made in Web AppBuilder. While searching adresses in "near me" widget it recquires the exact name of the adress. Earlier, it was possible to enter only a part of street and a lot of examples were shown. Right now, I have to enter all the letters from the street segment instead of this main segment that is, for example, the name of the street patron. I know there is an option to turn on/off "exact match" but its not working. there is no difference whether its on or off.
Maybe it's the fault of some AGOL update...
It is like that:
Earlier it was possisble to find that adress by entering only this: (it says "no results")
So...this is a pretty big change, if I configure a field in the map viewer like this:
you've effectively changed the meaning of "Contains" it no longer means "Contains" and is in fact more of a "starts with" query. We now have now way to search for tax payer names by last name in this situation.
Maybe you can provide a workaround to achieve this capability @RussRoberts ?
If you are using hosted and you are authoring a feature search post November release this will generate an index. If you are experienced with doing addToDefinition you can create the indexes this way. The index will then let you search any term within the defined field.
If no index exists then the search is then a starts with. This means it is no longer '%searched characters%' being sent to the service but is instead 'searched characters%'. If you want to use the leading % in a search you can enter that in the search widget and it will be treated like the old search.
We had to make this change to bring in performance improvements and hive stability. In testing we had samples where old search could take 5-10 seconds to return a result and then the index method returns results in sub second. Then the other factor was when we had content using the double wildcard search and search suggestions on layer-based searching. This also can become very expensive with increased search usage, # of characters being used in the search along with the number of characters in a field being searched. this then can lead to causing disruptions to your content.
One follow up question - what's the recommended approach to use the search widget in Dashboards when using non-hosted (arcgis server) services?
It looks like this same issue now happens in dashboards as a result of the update:
For example, typing "John" into a parcel owner field gives results:
But typing "Hast" gives nothing because of the missing wildcard:
| where | (LOWER(own_name) LIKE 'hast%') |
