Survey123 v. 3.23 web form refuses to use my orgs geocode services

Question

I have an existing Survey (web form) that did not have this issue in the previous version of Survey123, but after upgrading to version 3.23 web form, on most browsers on some devices, refuses to use my orgs published geocode services and will only use the Esri World Geocoding Service.  I am using the same published geocode services from my ArcGIS Server that had worked previously in the Survey and that currently work fine in our other Esri applications when accessed internally or externally on Chrome, Edge, Safari, etc.

In the Survey123 designer I have each of the geocode services setup in an Address component on my form.

Hoping someone else has recently experienced this behavior and has a solution around it.

LeeBrannon1 · Answer

Kind of an answer...so after I did more troubleshooting with survey forms using the Address question, it appears that there was nothing wrong with Survey123's Address question with regard to using my published geocode services - creating a new survey form from scratch proved that.  All worked fine.

My best guess then as to what went wrong in my existing survey form was that when i edited the form by removing the Map question and adding the Address question it caused some sort of confusion within my form - a glitch.

I'm going to chalk this up to operator error since there may likely be a method - that I'm not aware of - for editing a form for these two particular question types (Map, Address) and still have it work perfectly.

ZhifangWang · Answer

Hi @LeeBrannon1 ,

In the Survey123 July 2025 Update, the related change we made for the Address question type was using the latest ArcGIS Maps SDK for JavaScript, it should not change behavior of the question type.

Would it be possible to share a public survey URL that reproduces the issue so we can investigate further? You can send me a direct message with the survey link.

LeeBrannon1 · Answer

To add more context to my post, I just realized that a significant change I did make to my Survey for this new version was to remove the Map question and add in the Address question in its place.  The previous Map question had no issues with using my orgs geocode services, while the current Address question is experiencing the issue.  Does anyone know if the Address question is known to have issues using geocode services in a way that the Map question did not?