I am creating a parking map for my city with the search widget, using a feature layer for address points and an address geocoder. There are several issues that I am having, either while testing the search function under a live preview or after publishing the map which results in:
1) Searching for an address in the search bar results in multiple addresses being plotted and showing on the map, even if it is not the correct address.
2) The map does not pan to the results that appear in the results menu for addresses. I troubleshooted through this by enabling a trigger action in the search widget.
3) Clicking on 1 address in the results menu leads to the map panning to the first address selected, clicking on another address within the same results menu after that causes no follow-up action. I think I addressed this by adding in another trigger action within the search widget combined with the 1st trigger I added under 2)
I compared the Search Widget for my map between Experience builder and the old Web AppBuilder and noted that on Experience Builder, all the possible results immediately appear on the map which I am concerned could confuse somebody by the address results unless they start to click through the addresses. On the Web App, the results don't all appear at once and lets me cycle through the results one by one.
Additionally, I have the option to include a pop-up results menu when a location on is found on Web app builder which I definitely believe it helps clarify any potentially confusing results as the goal is for city residents to use the map to find public parking in their area. I do not see that option to enable a similar feature under the Search Widget on Experience Builder.
I am including screenshots here.
Can I recreate the same action on Experience Builder that Web App Builder produces?