Select to view content in your preferred language

Cannot add Arcgis World Geocoder to Search Widget in Experience Builder 11.3

333
6
05-27-2025 11:37 AM
TaylorDenniston2
Occasional Contributor

When I try to add the ArcGIS World Geocoder as the locator source in the the Search Widget, it just spins and never creates a connection. 

It only works with all my other sources, just not the World Geocoder. Any ideas?

0 Kudos
6 Replies
ShengdiZhang
Esri Regular Contributor

Hi @TaylorDenniston2 ,

Please add the following message actions to the search widget:

  • Record Selection Changes - Map - Zoom to
  • Records Created - Map - Show on map

I tested it in an 11.3 environment, and it looks good.

Regards,

Shengdi

0 Kudos
TaylorDenniston2
Occasional Contributor

Thank you ShengdiZhang for responding. What I meant by "it just spins" is the locator does not make a connection to the Search Widget. See the attached screen shot that shows the "busy" indicator. It will continuing displaying the "busy" indicator all day.

setLocatorSource.PNG

0 Kudos
ShengdiZhang
Esri Regular Contributor

Hi, are there any errors in the Console? You can find the Console in Chrome settings - Developer Tools:

ShengdiZhang_0-1748942442557.png

If you add the utility via URL, does it work?

Regards

Shengdi

0 Kudos
TaylorDenniston2
Occasional Contributor

I am getting an unexpected token request error? The URL for the locator is set to reference back to my portal for some reason? see attached.

ExB-locator-error.PNG

0 Kudos
ShengdiZhang
Esri Regular Contributor

We did have some known bugs related to utility login in 11.3, but this issue doesn’t appear to match any of them. Since I can't reproduce the bug on my side, I recommend reaching out to our Support team to help reproduce it.

In the meantime, could you try opening the locator URL directly to see if any warnings appear? Also, if you add the locator by URL (not choose from the Organization utility), does it work as expected?

0 Kudos
TaylorDenniston2
Occasional Contributor

I did try to the URL route, but unfortunately was meet with the same results. However, we upgraded to version 11.5 and it works now.

Thank you for all of your help with this issue.

-Taylor

0 Kudos