Survey123: pulldata("@property", 'token') problem

[JordanMiller4]

I implemented the reverse geocode function to an enterprise form but the pulldata("@property", 'token') function prevents our surveys from submitting to the server, displaying a red exclamation mark, signifying that it didn't go through. I can remove this from the form and it'll post to our server but   what could possibly go wrong?

hidden	signincheck	This field checks if the user is signed in.								pulldata("@property", 'token')
note	notloggedin	<b>You're not signed in to a named user account. This sample will only function when signed in.</b>								string-length(${signincheck}) = 0

[JamesTedrick]

Hi Jordan,

Is there a specific error presented?  One thing you could do is set the question that retrieves the token's bind::esri:esriFieldType to null to prevent that from being submitted but still accessible in the form.

[JAVIERVARA_SANZ]

Hi James.

We are having a similar issue retrieving the token through our inbox. The field is set to null, but we still want to retrieve the token when selecting the record from the inbox. We are using versions 3.9.148 (Field App) and 3.9.120 (Connect).

FYI, we are trying to check if a record in the inbox has been previously edited by another user through the same workflow, and prevent a second user from updating, submitting, and overwriting the same record. Assigning records to individual users won't work, so we are exploring this option.

Any guidance will be highly appreciated.

Thanks.

Javier