I'm using the Search widget in Experience Builder on one of our heavily used applications. After yesterdays update, the "zoom to" aspect of the search bar is broken. Instead of zooming to the address point, it takes us across the world to Europe.
Anyone else having this issue?
All I can think to do is turn off the zoom to option. But that doesn't resolve the issue.
Solved! Go to Solution.
@JudithWammack - I had to add this trigger action type where I had not had to before:
"To select a feature on a map that corresponds with a selected search result, add the Record selection changes trigger for the Search widget (when configured to use the results panel). Select the Data target, add the Select data records action, and configure it with the feature layer for the map and the fields that bind the connection between the trigger and action data. Additionally, you can add the Zoom to action to zoom the map to the feature."
Here's my planning data explorer:
https://experience.arcgis.com/experience/4231009432fd447da27cce87e5c6febf
and a PID:
2027070041
So now the app does zoom to and then pan to, although there is still some kind of lag out there because when I enter in a second PID, it does not always clear the map right away and pan. The user has to click the search result again.
"So now the app does zoom to and then pan to, although there is still some kind of lag out there because when I enter in a second PID, it does not always clear the map right away and pan. The user has to click the search result again."
This is exactly my issue right now. It wants to keep zooming into the first search when I do a second search.
These are my actions right now. I have it where when you search an address it will select a parcel that is associated with that address.
I have another one where if you search a subdivision name it will select all the parcels that is associated with that subdivision name.
Yeah @JudithWammack - these interactions get tricky what with having to mix locator and layer sources, and then the actions to feed NearBy's and / routing.- which I have as well, just in other ExB. I'm having to go through all of them....But that looks right to me.
I am noticing that our custom locator that we use on AGOL is now plotting all our addresses to Africa. The same locator still works on our Enterprise portal and the 3rd party applications that use it as well. The user who reported it said it was happening yesterday but sort of started working correctly by the end of the day; however this morning, the odd behaviors is back.
Hi @MathiasHudock - I'll have to test that out as I'm not certain what you did is the solution for everyone. I have some interactions and triggers set to go to widgets on multiple pages in some of my apps and I can't necessarily use the option to Interact with a map widget in all cases.
This bug should be fixed in today's update. Please let me know if you can still reproduce it.
Thanks,
Shengdi
@ShengdiZhang It is fixed!! Amazing! Thank you!