Hi @Anonymous User and @LarryWiebe,
I was wondering if there are any news on BUG-000127130 (or if you heard of smart ways to go around it).
I am also trying to overwrite the inbox geopoint location (i.e. the actual geometry) without success.
My use case is strictly about creating new surveys from the inbox (create a new survey by reusing an existing one).
- At geopoint creation time, the calculated coordinates work well for point creation (=> they are well formatted).
- At geopoint update time in the 'new' survey, the geopoint question does not replace the coordinates: the original geometry remains.
If my form used a map, instead of calculated coordinates, users would be able to edit the existing point (drag around, or delete and create new) ... so Survey123 seems to be able to overwrite the geometry in some cases.
- However, if I do expose the map in the form, the update isn't effective either : users must push the update button, then the geopoint responds to changes in calculated coordinates.
- Having parametered with 'calculateMode=always' is not helping, the first update ni calculated coordinate is not resulting in a geopoint update.
- Using of second (null) geopoint field, based on the property 'status' is not helpini either: status is null when you create a new survey from the inbox.
This is observed using S123Connect 3.13.251 and Survey123 Fiel App (on PC) 3.14.255.
A simplified example form is attached.
Many thanks for any help!
With kind regards,
Hélène.
P.S:
My use case is a form without any exposed map. The point location is derived from selected values in a select one field.
The form is long and tiedous (per work order ^^), and people will default to creating new surveys from existing surveys from the inbox.
The issue appears here: because the geopoint geometry is not overriden by the newly selected location, my output map has a few piles of many points each 😞