Survey123 connect: use reverse geocoded address to overwrite original address

[NataliyaLys]

I created a survey in Survey123 connect. There is a text question, 'Enter report address' question with a geocode appearance, for user to enter an address. Once user enters an address, the address is then shown on the map, which is a geopoint question that pulls X,Y from the original geocode question. All this works great. 

Next, I want the user to be able to open the map and move a pin of the map if needed, which also works. And once the pin on the map is moved I would like the original geocoded address to be updated with the new reverse geocoded address pinned on the map. In the image below, by original address is: 2211 Howard St, Omaha, NE 68102 and after the user opened a map and adjusted/moved pin the new (reverse geocoded) address is now: 661 S 26th Ave, Omaha, NE, 68105. 

So I would like the original address to be overwritten with reverse geocode address. I've tried a few things but cannot get it to work. Any suggestions/ideas on how to accomplish this are greatly appreciated. 

Thank you,

Nataliya

[Neal_t_k]

Not sure you are going to be able to accomplish this as you describe, any attempt to recalculate the original address question based on subsequent map questions results in a cyclic dependency.  

One option could be to get rid of the the original "enter report address" question and start with the map itself.  When a user clicks on the map, they have the option to search an address from within the map.  They can fine tune from there, and then have your question labeled "rev geocode" be your final answer.

Your other option is to leave as is and just use the "rev geocode" as your final address.  Label it as "revised/adjust address"   You could even null out the "enter report address" question so it doesn't get submitted to feature layer, so you only have one address in the data.

[NataliyaLys]

Thank you for sharing your ideas. I was afraid that was going to be an answer. I'm going to test some of these options and see which one works better and would be simpler for the end user, specially on mobile devices.