Hi @CRossNSDA
Maybe you tried these, but just in case,
Ensure that your app, widget, or geocoding request explicitly references your custom Locator View, not the default World Geocoding Service.
In web maps or apps, go to Settings > Utility Services > Geocoding and set the custom Locator View as the default locator for your org or app.
Go to Content > Locator View > Settings in ArcGIS Online(if that is what you are using).
Confirm that under Locate settings, only the intended country is checked.
Check that the “Enable suggestions” and “Enable place finding” options are configured correctly.
Hey @CRossNSDA I saw you are using survey123, are you building the survey using connect or the web? And could you test submitting thr survey from the web instead of the app sometimes they act differently?
I tested with both web and the application. Same result for both.
@CRossNSDA so sorry about that!
Was the survey created using Connect or the web designer?
I created a separate survey in both and had the same issue.
ah okay. Could you share the steps you followed to add/use the locator in the survey?
@CRossNSDA Do you get the same behavior when you create a locator view in ArcGIS Pro?
https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/add-a-locator-view-to-a-project.htm
Where will you be using the locator view? (map viewer, web app, ArcGIS Pro, mobile)
I will test in ArcGIS Pro but we are trying to use the locator view in Survey123 field app.
I created a locator view in ArcGIS Pro and it works as intended. When I try and utilize the views that I created in ArcGIS Online, they do not act as expected. I followed similar steps as defined here: Configure a locator view for your organization