Latest Contributions by PaulCone

It appears that it does not reorder the fields in the underlying database. ... View more

I can't find it documented, but I just tried it in 1.2, and it works. ... View more

I was at the UC last week. At the closing session, Jack said, “I think by next summer most of you will be running on Pro.” Pro lets you do this. Even though they’re very clear they’ll be supporting Desktop for a while, I seriously doubt they are going to put the effort into retrofitting it for this feature. I’m guessing it would be a major code change. ... View more

Someone at ESRI gave me the following informal suggestion... "ArcGIS Online and Collector use editing templates (which are defined in ArcMap).  Editing templates require a default value.  So, when you define a field with “Allow NULL Values” equals “No”, and do not specify a default value, then default values are added to the template when the service is created. These default values are a space (“ “) for text fields, a zero (0) for numeric fields, and a date in 1899 for date fields. You can see this by creating a service with “Allow NULL Values” equals “No”, no default values, publish the service, and then have a look at the template section of the service REST URL JSON. Development is aware of this issue and is working on a solution. However there is no target date. The challenge is that this issue is not limited to Collector – it really is an ArcGIS platform-wide issue. There really is no good workaround, but one “workaround” that you may want to consider is: Specify default values for all fields (ArcMap will do this in the editing template if you don’t). Use CAPS for required field names, so that it is more obvious for users. Set defaults for text fields to something like “REQUIRED”, and for numeric fields to something like -99. And then train your users that a field name in CAPS is required. Another workaround, although risky and with its own issues is to edit the default values out of the template. This blog and linked doc explains how to open up the REST URL JSON in admin mode: http://blogs.esri.com/esri/arcgis/2014/10/19/updating-hosted-feature-services-in-arcgis-online/  You need to be careful, as if you make a mistake you will corrupt the service. So make sure you can easily recreate the service! For example, your service looks something like:   "templates" : [     { "name" : "Required_Test",       "description" : "",       "drawingTool" : "esriFeatureEditToolPoint",       "prototype" : { "attributes" : { "DOUBLE_R" : 0,           "TEXT_R" : " ",           "DATE_R" : -2209161600000,           "TEXTDOMAIN_R" : " " }       }     }   ], Using the admin capability, go and delete all the attributes under that have a default field setup and change the last edit data to “”  (There is an issue with the last edit date at the top – if you don’t change it to "" you will get a validation error). The edited template section would look something like this: "templates" : [     { "name" : "Required_Test",       "description" : "",       "drawingTool" : "esriFeatureEditToolPoint",       "prototype" : { "attributes" : { }       }     }   ], Here are the screenshots of the required fields. You will see the required text and the submit button disabled. After you fill out the fields and have a valid location the submit button will activate. This is a bit of a hack. What you will notice is that editing the template breaks the editing in ArcGIS Online." ... View more

I'm still not clear what your question is. ... View more

Such as? ... View more

So I talked with ESRI about this.  The issue is, there's a template that gets created in the Layer Definition, that Collector is using is populating the all the fields, even the mandatory ones.  It's beyond a Collector issue, and more of an AGOL issue, that they said they'll work on a solution, but in the meantime you can work around it by going into admin mode and doing Update Layer Definition and then deleting the default values out of the template. ... View more

I emailed a Solution Engineer in the Olympia office who has seen my implementation and he said he's asked the development team about this. ... View more

I just had my colleague test this on his Android phone and it is not requiring the fields as it should, so I am suspecting this is not an iOS specific thing.  I did post about this on a thread earlier this year but I haven't heard anything since. Re: Collector can't handle required fields, i.e. Nulls Not Allowed? ... View more

Did you ever get mandatory fields working?  I coulda sworn it was working when I first started on my project in the spring, but now it is not. Paul ... View more

I have written a Python script to do exactly this, for post-earthquake building safety inspections.  Yes, you can't use a field on the feature because of the one to many relationship.  I have a layer that is used just for symbology on the map and it not editable in Collector.  It runs in a loop.  Here are the steps. # Queries AGOL service for new ATC-20 building inspection records collected with ArcGIS Collector. # Adds new inspections to table in local geodatabase. # Updates inspections with precalculated lat/long values from building footprints. # Downloads photos attached to inspection records and adds them to geodatabase. # Updates inspected buildings layer on AGOL feature service. Paul ------------------------------------------- Paul Cone Corporate GIS Bureau of Technology Services City of Portland, Oregon paul.cone@portlandoregon.gov ... View more

I started a project in April and the required fields were working correctly in iOS then, but they are not now.  I have suspected ESRI broke something with an update, as we are using a hosted service.  This is a good clue.  I will test on Android and report back. ... View more

You might post this question at Esri/arcgis-osm-editor · GitHub. ... View more

I think the space issue is perhaps new.  I noticed that in the table as well, and I didn't see that happening before 10.3.1.  So maybe this is the cause. I also just changed the service I am working on and made CreateDate and EditDate required fields and now my Submit button is greyed out.  So it seems the functionality still working overall. ... View more

Well, the extra space thing is a different annoyance, but in this case it is a picklist.  The user must choose one of the options for the record, but Collector is no longer enforcing it. {   "name" : "Posting",   "type" : "esriFieldTypeString",   "alias" : "Posting",   "sqlType" : "sqlTypeOther", "length" : 20,   "nullable" : false,   "editable" : true,   "domain" :   {     "type" : "codedValue",     "name" : "PostingPlacard",     "codedValues" : [       {         "name" : "Inspected (Green)",         "code" : "Inspected"       },       {         "name" : "Restricted (Yellow)",         "code" : "Restricted"       },       {         "name" : "Unsafe (Red)",         "code" : "Unsafe"       }     ]   },   "defaultValue" : null }, ... View more