POST
|
I'm not sure if I understand the answers on all these different cases. For me, I have a web map that contains three editable layers (point, polygon and polyline fcs from the same database). All of them have a field TYPE that use the same coded value domain. All these three layers work fine in Collector, but I have a fourth layer (read only) from the same database that won't show. This layer does not use the same coded value domain or have a TYPE field. Then, my fifth layer (read only) from another database shows up just fine. All the featurelayers in the webmap is published on a standalone ArcGIS Server, and registered as items in Portal. There is a lot of talking about updates to ArcGIS Online in this thread, but what about Portal? What could be the cause to the problem I see? Everything works just fine in Collector Classic
... View more
05-02-2019
06:30 AM
|
1
|
0
|
216
|
POST
|
Thanks, yes, this checkbox was turned on. Turning it off made it work 🙂
... View more
07-10-2018
04:30 AM
|
2
|
0
|
1258
|
POST
|
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
... View more
07-10-2018
01:27 AM
|
0
|
0
|
1258
|
POST
|
I launch Survey123 from Collector with this url passing an objectnumber into Survey123 with the url: href="arcgis-survey123://?itemID=985fc4058b6d3dd3a491&field:OBJECTNUMBER={OBJECTNUMBER} This OBJECTNUMBER is an integer, and is passed into a field in my survey that is of type esriFieldTypeInteger. Problem: In iOS, this integer is formatted with a space as thousands separator inside the field in Survey123. When the survey is submitted, it seems that this formatted integer is not recognized as an integer by the feature service. No error message is given, but no value is written into this field. In Survey123 on Windows, this formatting does not occur, and everything works. Is there a way to avoid this happening in iOS?
... View more
07-06-2018
12:37 AM
|
1
|
13
|
1959
|
Title | Kudos | Posted |
---|---|---|
1 | 05-02-2019 06:30 AM | |
1 | 07-06-2018 12:37 AM | |
2 | 07-10-2018 04:30 AM |
Online Status |
Offline
|
Date Last Visited |
11-07-2022
07:48 AM
|