AnsweredAssumed Answered

Can't set integer to null with Feature Service REST update

Question asked by geonetadmin on Sep 7, 2012
Latest reply on May 5, 2017 by andrewn
Original User: oppedahl

I have a feature class published to a 10.1 Feature Service with one of its attributes a nullable integer with no default value defined. I'm trying to edit the attribute with the REST API's Update operation. It works if I set it to a number, but saving null doesn't work. There's no error--the call goes through fine--but the value remains unchanged. Is it not allowed to set a numeric field to null once it's been set to something else? I can set it to null just fine in ArcMap. Here's a snippet of the JSON I'm sending to the update:

[
{
"attributes": {
"OBJECTID_1": 1234,
"AnInt": null,
}
}
]

Outcomes