Trouble with Geocode appearance in version 3.13.234

[ShelbyZelonisRoberson]

Hi - I have had a public-facing Survey123 form in production since the beginning of the year. It uses the geocode appearance on a geopoint field, which used to work in the beta version. However, when 3.13.234 and the full functionality of the geocode appearance was released, my survey broke and I can't get it to work properly anymore.

My main problem is that I need the field that has the geocode appearance to be a geopoint question (mapped on the backend). It seems like the new version only works if the appearance is used on a text field, in which case my data isn't mapped on the backend. This ruins my whole workflow because the whole point is to map the data in a dashboard. How can I get the Survey back to working with geopoint capturing the geographic data while also using the geocode appearance? This is a major issue right now because all new data being collected by the public is not getting mapped (and many other consequences). 

Thanks!

@JamesTedrick 

@IsmaelChivite 

[BarbaraWebster1 · Accepted solution]

Hi Shelby,

You can populate your geopoint using pulldata() to extract the coordinates from the text question that has the geocode appearance. I attached an XLSForm with an example of that workflow.

Depending on your workflow, you may want to add a hidden appearance to the geopoint or set it to read-only.

Thanks,
-Barbara

[IsmaelChivite]

@ShelbyZelonisRoberson  To add to @BarbaraWebster1 's response above:

• The geocode appearance was in Beta until we released 3.13. To address feedback we received during Beta testing, we changed the way he geocode appearance works.
• You will need to change your XLSForm.
• For an overview of how geocode works now I suggest you read: https://community.esri.com/t5/arcgis-survey123-blog/survey123-tricks-of-the-trade-addresses-and-the/...

[ShelbyZelonisRoberson]

Ah, exactly what I was looking for. Thanks to you and @BarbaraWebster1  both!