I use the 3.0 version of Survey123. iPhone uses Norwegian language and region settings. We don't really use a thousands separator, but I see that the iPhone is formatting numbers using a space to separate the thousands. Today, I tried this on an Android phone as well, and the same happens here
Submitting surveys works fine as long as this integer is not formatted with a space. When I launch it from Collector, I have to remove this space before submitting, then it's ok. Problem is that I want to set this field to read only.
When the integer enters the form and gets a thousands separator, the number turns red indicating that the content does not match the field in the form that is of type esriFieldTypeInteger. Nevertheless, I am able to submit the form without any error message from the app, and a record is added to the database without a value in this OBJECTNUMBER field. I think there should be a mechanism in the Survey123 app that prevents submission of the form when the input does not match the form's field types
In the Survey123 form, this field has type=integer, required=yes, bind::esri:fieldType=esriFieldTypeInteger
Jostein