Feature Layer update kills the save

Question

I have a FeatureDataForm with and EditEnded handler like this.private void MyFeatureDataForm_EditEnded(object sender, EventArgs e)
   {
   foreach (Layer lyr in MyMap.Layers)
    {
    if (lyr is FeatureLayer)
     {
     FeatureLayer featureLayer = lyr as FeatureLayer;
     featureLayer.SaveEdits();
     featureLayer.Refresh();
     featureLayer.Update();
          }
    }      
   }

This cycles through all the FeatureLayers on the map and attempts to refresh them. Supposedly I only need the Update() command to do this but the SaveEdits() and Refresh() commands are in there for experimentation. I found that there is no benefit from the first 2, however if the Update() command is included the edit which was just made seems to get cancelled and nothing changes on the map or its data. Client caching is off and IsReadOnly is set to false. Anybody know what gives here?

Thanks

JenniferNery · Answer

You can go through the API's Library Reference http://help.arcgis.com/en/webapi/silverlight/apiref/webtoc.html# and go through the samples. I'll ask around if we have other online documentation that can help you see order of events or general workflow.

DonFreeman · Answer

Jenn -

Thanks so much. That solves my problem.
I am finding it somewhat frustrating to "discover" the order in which things execute. Is there a white paper or something somewhere where I could have discovered this myself?

Thanks

JenniferNery · Answer

FeatureDataForm's EditEnded event fires before FeatureLayer's EndSaveEdits.

The changes made in the layer need to be pushed to the server before you can re-query the service. You can call Update() in EndSaveEdits eventhandler but also know that any change on the layer cause your application to re-query the service which is expensive. You can maybe use a boolean to flag whether the attribute that was changed need to call update.