Using device location for second geopoint when using in URL scheme

Question

I have a survey with two geopoint questions:

* The first geopoint represents the location of an asset in the field and is set by using the center parameter of the Survey123 URL scheme, and this is submitted as the geometry value for the the survey point. The user clicks a point in Field Maps, then the lat/long from that point is passed to the URL in the popup to become the survey point geometry. In other words, the survey point geometry is identical to the geometry of the clicked point in Field Maps. So far so good.
* For the second geopoint question, we want to grab the device location and write lat/long to fields in the table. So we set the bind::esri:fieldType to null and set a calculation on two decimal fields using pulldata from the second geopoint.

The issue is that the "center" parameter seems to set the location of both geopoints when the survey is opened, rather than just setting the location of the non-null (default) geopoint question.

If the user clicks the locate button on the second geopoint, it recalculates and the correct values are passed to the decimal fields. But we need to automatically grab the device location without relying on the user clicking the second geopoint question (in fact, we would prefer to hide it entirely) to reset the location.

Is there a solution to this?

JRhodes · Answer

Thanks again Doug, very good point. I'm planning to use the pulldata("@property", 'mode') calculation on a hidden/null question to assign the survey mode to a variable, then use that variable in the relevant column for the second geopoint and the lat/long fields populated from it (e.g., ${survey_mode}!='edit')). This way those fields will only be calculated on initial submission.

dougbrowning · Answer

I would test edits if you set calculationMode=always since it may change it if anyone edits any field later on.

One idea I used in another form is pull the lat/long then set a constraint to make sure the second point is not in the same place as the first.

JRhodes · Answer

@DougBrowning Setting the default to 0,0 still placed the second geopoint on the &center= value. However, setting calculate to null and bind::esri:parameters to calculationMode=always (then making the second geopoint required) worked for me. Thanks for putting me on the right track.