AnsweredAssumed Answered

Trouble getting attributes to go to the server

Question asked by recrawford on Mar 23, 2015
Latest reply on Sep 2, 2016 by MBranscomb-esristaff

Anybody else having trouble getting attributes to go to the server when creating records on a table hosted in a feature service?  Here is a code snippet for it:

 

ServiceFeatureTable _sft = await ServiceFeatureTable.OpenAsync(myFeatureServicePath);

GeodatabaseFeature gf = new GeodatabaseFeature(_sft.Schema);

gf.Attributes["WR_ID"] = 1;

// more attributes go here

 

if (_sft.CanAddFeature(gf))

{

  long oid = await _sft.AddAsync(gf);

}

 

FeatureEditResult fer = await _sft.ApplyEditsAsync(false);

 

foreach (FeatureEditResultItem ri in fer.AddResults)

{

  if (ri.Error != null || !ri.Success)

  {

  return false;

  }

}

 

return true;

 

I am running ArcGIS Runtime for .NET 10.2.5 with a feature service running on ArcGIS Server 10.2.2.

 

When I use fiddler, the ApplyEditsAsync only sends up the ObjectID attribute and you don't see any other attributes I might have in there.  I'm not sure why I don't get other attributes (like WR_ID, in this case) to go.  Any ideas?  Thanks!

Outcomes