topic Re: survey123 error code 1000 - conversion failed when converting from a character string to unique identifier in ArcGIS Survey123 Questions

survey123 error code 1000 - conversion failed when converting from a character string to unique identifier

Anonymous User — Thu, 19 Apr 2018 15:16:07 GMT

I am looking for more information on this error code. This form is writing to a related table in a feature service hosted in AGOL. I built the survey in Connect Version 2.6.4 and it is being used on iPads and the desktop application.

Re: survey123 error code 1000 - conversion failed when converting from a character string to unique identifier

JamesTedrick — Thu, 19 Apr 2018 19:35:52 GMT

Hi Andrew,

I see that your form has a hidden question called REL_GlobalID - how is this getting populated? Given the error code (converting an answer into a unique identifier), it most likely relates to this question (which is outputting to a GUID field).

Re: survey123 error code 1000 - conversion failed when converting from a character string to unique identifier

Anonymous User — Thu, 19 Apr 2018 19:50:15 GMT

I am using the survey123 costume URL schema to pass the field REL_GlobalID. Users are accessing the survey from hyperlink in the point features pop-up from our WebApp.

arcgis-survey123://?itemID=9ca813b0c3664fafb2014aae3f17a08b&field:SWMID={SWMID}&field:GenBMPType={GenBMPType}&field:SpecBMPType={BasinType}{InfilType}{FiltrType}{MTDType}{MTDFilType}{MTDHydType}{MiscType}&field:BMPFunc={BMPFunc}&field:Rel_GlobalID={GlobalID}

The error is only intermittent, we have submitted many surveys successfully.

Re: survey123 error code 1000 - conversion failed when converting from a character string to unique identifier

JamesTedrick — Thu, 19 Apr 2018 19:55:18 GMT

Thanks Andrew,

I suspected this might be the case. If you change the hidden question to a text question, do the GlobalIDs display with curly braces already? This can occur depending on the application launching Survey123 and Survey123 will try to automatically add the curly braces. We are working to prevent this from being an issue in the future, but in the meantime, this can be worked around:

1. Have the value load into a hidden question with fieldType of null . Let's call this question incoming.

2. Have the REL_GlobalID question be a calculate question that checks for curly braces and removes if present:

if(regex(${incoming}, '^\{[\w\-]*\}$'), substr(${incoming},1, string-length(${incoming}) - 1), ${incoming})