Skip to main content
Solved

Can't Write values to ArcGIS Online Feature Services

  • December 15, 2016
  • 8 replies
  • 116 views
mmccart
Contributor
Forum|alt.badge.img+16

This morning, FME Server started to throw errors writing <NULL> values to numeric values using the ArcGIS Online Writer. Everything was working until Esri upgraded AGOL overnight. We've submitted a ticket to Esri, but wanted to submit a question here as well.

The error we're getting is: ArcGIS Online Feature Service Writer: 'addResults' error for a feature in 'AVL DB'. The error code from the server was '1000' and the message was: 'Attribute 'Right Wing Plow State' has an invalid value of ''. The value should be data type esriFieldTypeDouble.'

We were able to successfully add a feature via the REST API using the following:

[ { "geometry" : {"x" : -94.44920, "y" : 41.88339}, "attributes" : { "LABEL" : "Test Insert", "RIGHTWINGPLOW" : null, "ACTIVE_MATERIAL" : "NONE" } } ]

Does anyone have the syntax needed to write version of a <NULL> value to AGOL?

Thanks,

Mark

Best answer by mmccart

Got notification from ESRI today that they will be fixing this bug later tonight. For reference: BUG-000101505 : Add Features request fails for ArcGIS Online Hosted Feature Service when using empty quotes to pass a NULL value to a field type of Double or Single/Float.]

View original
Did this help you find an answer to your question?

8 replies

mmccart
Contributor
Forum|alt.badge.img+16
  • mmccartContributor
  • Author
  • Contributor
  • Best Answer
  • December 15, 2016

Got notification from ESRI today that they will be fixing this bug later tonight. For reference: BUG-000101505 : Add Features request fails for ArcGIS Online Hosted Feature Service when using empty quotes to pass a NULL value to a field type of Double or Single/Float.]

nic_ran
Contributor
Forum|alt.badge.img+16
  • nic_ranContributor
  • Contributor
  • December 19, 2016
mmccart wrote:

Got notification from ESRI today that they will be fixing this bug later tonight. For reference: BUG-000101505 : Add Features request fails for ArcGIS Online Hosted Feature Service when using empty quotes to pass a NULL value to a field type of Double or Single/Float.]

Thanks for posting this, I thought I had a data issue on my end and was trying to figure it out. Do you have things working now? I don't have access to the ESRI support site to check the bug status but I'm still having trouble writing nulls..

 

 

jfisch25
Contributor
Forum|alt.badge.img+10
  • jfisch25Contributor
  • Contributor
  • December 19, 2016

I've been searching for that bug on ESRI Support, but I can't find it anywhere. Hope it gets resolved soon.

nic_ran
Contributor
Forum|alt.badge.img+16
  • nic_ranContributor
  • Contributor
  • December 20, 2016

ESRI Canada informed me that the bug had been marked resolved late yesterday afternoon but I'm still not able to load data. I have not had any more feedback from them yet.

nic_ran
Contributor
Forum|alt.badge.img+16
  • nic_ranContributor
  • Contributor
  • December 20, 2016

More feedback from ESRI Canada and they confirm that the issue still exists. They are going to follow up with ESRI USA.

One point of note: ESRI claims that if the value <null> is passed, instead of an empty string, this process should work. I have ensured that the value I am passing to the FME AGOL Writer is <null> but the writer is converting this to "". Perhaps someone from Safe can comment on why this is being done?

fmelizard
Contributor
Forum|alt.badge.img+17
  • fmelizardContributor
  • Contributor
  • December 20, 2016
nic_ran wrote:

More feedback from ESRI Canada and they confirm that the issue still exists. They are going to follow up with ESRI USA.

One point of note: ESRI claims that if the value <null> is passed, instead of an empty string, this process should work. I have ensured that the value I am passing to the FME AGOL Writer is <null> but the writer is converting this to "". Perhaps someone from Safe can comment on why this is being done?

 

So we checked into it and longer ago, the way to pass NULL was the send in an empty string. But we think we can just use a variation of the newer API and send in truly a NULL. We're making the change to FME 2017 beta now. Sadly won't be able to help all y'all that are using 2016 or older but at least moving forward we can win. Ideally the backwards compatibility can be maintained for AGOL to still honor an empty string as meaning NULL -- I'd be surprized if FME were the only client that was doing this.
nic_ran
Contributor
Forum|alt.badge.img+16
  • nic_ranContributor
  • Contributor
  • December 21, 2016
nic_ran wrote:

More feedback from ESRI Canada and they confirm that the issue still exists. They are going to follow up with ESRI USA.

One point of note: ESRI claims that if the value <null> is passed, instead of an empty string, this process should work. I have ensured that the value I am passing to the FME AGOL Writer is <null> but the writer is converting this to "". Perhaps someone from Safe can comment on why this is being done?

Thanks Dale. Hopefully ESRI can do something to help out for current versions of FME.

 

 

nic_ran
Contributor
Forum|alt.badge.img+16
  • nic_ranContributor
  • Contributor
  • December 23, 2016

ESRI have now resolved the issue and I was able to write features with empty attribute values.

Reply


Most helpful members this week

Community Stats

30,846
Posts
116,941
Replies
38,670
Members
Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.