Updates in JSON feature service edit not taking

jameshickey · ‎02-08-2017

I am trying to use the POST process to update the JSON for a feature service on ArcGIS Online. A detailed procedure on this process can be found here: https://blogs.esri.com/esri/arcgis/2014/10/19/updating-hosted-feature-services-in-arcgis-online/#com...

I am trying to change the field editable to true in the following JSON.

{
 "name" : "FACILITYID", 
 "type" : "esriFieldTypeString", 
 "alias" : "Facility Identifier", 
 "sqlType" : "sqlTypeOther", 
 "length" : 20, 
 "nullable" : true, 
 "editable" : false, <--- CHANGE TO true
 "domain" : null, 
 "defaultValue" : null
 },

Everything seems to run okay. I don't get any response only a blank page with the name of the layer
The change does not stick in the feature service howerver. 
Any ideas?

Published with ArcMAP 10.4.1 and Windows 7.

Thank you,

James

jameshickey · ‎02-09-2017

Updating to let people know there is now a BUG logged with ESRI and it is currently under review.

BUG-000102784
Cannot change field editable value by updating service definition from REST end point

Current workaround is to edit field properties in ArcMAP and republish.

View solution in original post

jameshickey · ‎02-09-2017

Updating to let people know there is now a BUG logged with ESRI and it is currently under review.

BUG-000102784
Cannot change field editable value by updating service definition from REST end point

Current workaround is to edit field properties in ArcMAP and republish.

deleted-user-LNABNwA5CZcD · ‎10-02-2017

I'm pretty much hitting the same issue, just with trying to edit the "nullable" field from false to true. Was this never fixed?

Anonymous User · ‎09-06-2018

Has this issue been addressed?

KhaledHassen · ‎09-10-2018

Currently you can only change the field visibility, domain and field alias. All other field properties cannot be changed once you publish the layer. We will add support to set field editable property. But we will not be able to support making a field NOT Nullable or Nullable since this operation relies on the data and affect the data store schema. You can work around this by creating a new field with the property you want, then use layer Calculate API to copy the data.

Anonymous User · ‎09-20-2018

Wow so if we need to make a field Not nullable we have to republish and repoint all our features.....awesome. Just a note onto what you said: you can change the names in the domains, but not the order.