Hi, I was hoping someone might be able to provide some insights into dealing with esriFieldTypeGUID fields. I have an esriFieldTypeGUID geodatabase field, exposed by a survey form's bound esriFieldTypeGUID text field...but am getting an error submitting a form with this field populated. Hopefully an easy one - but does this value need to be manipulated in the form before submitting?
Solved! Go to Solution.
Hi Sam,
The issue revolves around whether or not the curly braces are supplied as an incoming value - Survey123 expects them not to be present, but some applications supply them. To allow for the survey to accept either with curly braces or not, here's the workaround:
The survey should be designed with 2 fields to handle the globalid value:
if(regex(${incoming}, '^\{[\w\-]*\}$'), substr(${incoming},1, string-length(${incoming}) - 1), ${incoming})
Hi Sam,
The issue revolves around whether or not the curly braces are supplied as an incoming value - Survey123 expects them not to be present, but some applications supply them. To allow for the survey to accept either with curly braces or not, here's the workaround:
The survey should be designed with 2 fields to handle the globalid value:
if(regex(${incoming}, '^\{[\w\-]*\}$'), substr(${incoming},1, string-length(${incoming}) - 1), ${incoming})
Thanks, James for clarifying the issue. That workaround solves it.