ExB search widget issue

[JosephRhodes2]

I've configured an ExB app with a search widget that allows users to search for a property development by name or permit number, then populate a Feature Info widget with the popup for the selected result, using a data view for the developments so the map features don't get filtered.

Everything works great, except I had to set the search suggestions to 0 because when the user starts to enter another search term, the suggestions immediately show "No results found...", because the layer source has been filtered by the widget. If they press Enter or click the search icon, the correct results are returned because this clears the filter and initiates a new query.

Am I just out of luck if I want to have suggestions enabled for successive searches? Users can click the X to clear the results, but this is unintuitive and user testing has shown that they usually don't think to do this, they just highlight the text in the box and start typing a new search term. We basically just want it to work like the WAB search.

[TonghuiMing · Accepted solution]

Hi @JosephRhodes2 - Unfortunately, what you have observed is the current behavior of the layer search.

However, it does make sense to clear the search immediately when the users remove all the content. We will keep a note and evaluate if it can be enhanced later. Thank you for bringing this up.

[TonghuiMing]

Hi @JosephRhodes2 - this should be enhanced with the latest AGOL 10.3 release. Now clearing the search content will remove all the previous search results.

[JosephRhodes2]

Thanks @TonghuiMing, but it still doesn't work the way we need it to. It seems the user needs to clear the text by pressing delete or backspace. If they just highlight and start typing a new search term, which is how I believe most people would do it, it still returns no results.

We would really love a search widget that just works like Web AppBuilder, which allows multiple successive searches no matter how the user interacts with it, because it doesn't filter the data. An option to open the popup like you can do in WAB would be nice as well.

[TonghuiMing]

Unfortunately, that behavior will not change for now, since there are other users who do not want the results to be cleared out entirely, e.g., they want to look at the previous result on the map when searching for a new one. And that's the only workaround they have - "to just highlight and start typing a new search term".

[JosephRhodes2]

Thanks @TonghuiMing; however, this is different from the way search tools work in all other Esri products and across the internet in general. The filtering behavior should be optional. The JS API Search widget does not automatically filter results, nor does the search functionality in the other 4.x configurable apps. The user preference you mention ("want to look at the previous result on the map while searching for a new one") is satisfied if you don't filter the results. I'm not talking about clearing the map features, I'm talking about being able to get results returned for a new search term.

The average public user is expecting a Google Maps/Bing Maps experience. If I search for a restaurant by name in Google Maps, it doesn't filter other nearby restaurants. And if I want to search for a different restaurant, I simply start entering another search term. 

[TonghuiMing]

Hi @JosephRhodes2 - we will keep a note of these details and further evaluate if we can enhance the behavior in the upcoming releases. Thanks for staying with us.

[NathanRenn1]

I would like to reiterate everything mentioned in this post. Why the search widget in ExB does not function like WAB is baffling. I should be able to choose whether to filter the layer or not, adding the layer again as a work around is insane. We should have the option to display the popup on finding the feature not build an info widget to do the thing the map is already doing if I just clicked on a feature. Honestly this search widget feels like it was designed by someone who has never used a search bar ever.

[JonathanLee]

I agree that mimicking the WAB search widget functionality would be great (posted separately: https://community.esri.com/t5/arcgis-experience-builder-questions/search-widget-with-layer-source/m-...). 

For example, when someone searches a parcel and selects it from the search widget, the geometry for all other parcels "disappears" because it functions as a filter. Very easily could be confusing to the average user why the other parcels are "disappearing" because they're just wanting to find a parcel, not necessarily filter.

[NedCake1]

If the Search Widget cannot be configured to select a feature from the map and deploy a popup for the selected feature, then the Search Widget is not complete. Having to create a separate feature info widget instead of using the awesome html/arcade popup that I've already developed is not helpful.