Thank you. It took some reading to figure out how to get the reverse geocoding to work with Portal 106 due to an error or bug. But I found this workaround by Johnathan Hosthorpe and it's working.
https://community.esri.com/groups/survey123/blog/2018/07/06/understanding-reverse-geocoding-in-surve...
If you sign into a portal that uses the default geocode service configuration (i.e the inbuilt Esri World Geocoder item is at the top of the list in the portal settings) - you will get an error when trying to perform a reverse geocode using pulldata("@GeoPoint",${location},"reversegeocode") if you do not specify a URL parameter. This is because the app will use the first locator service in the portal list and if it is the default World Geocoder it will require a token (even though the service is public).
To get this working the user must create a proxy item in the portal and put this at the top of the locator list. See: https://docdev.arcgis.com/en/survey123/desktop/create-surveys/geopoints.htm#ESRI_SECTION1_E89036D9C3...
Steps
- Create an item in the portal org that links to the url for the world gecocode service (https://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer) and has AGOL credentials saved into it. The credentials must be for an AGOL org user that has the permissions to perform geocodes (Geocoding).
- Create a new locator in the portal based on the service URL of the item created above and add it the top of the locator list.
- This will now be the default geocode service for the portal and will work for reverse geocodes (where a url paramter is not specified in the function).
