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