Latest Contributions by CharlesMacleod

Hi Scott, there are two patterns available with edit operations: First: Using specific coarse-grained methods that do very specific kinds of edits - such as Create, Clip, Cut, Modify, etc. (https://github.com/esri/arcgis-pro-sdk/wiki/ProConcepts-Editing#performing-edits-with-editoperation). This is the preferred pattern. Second: There can be cases where your data spans GIS and non-GIS data that you need to edit atomically (within a single edit operation) and for this purpose there is the edit operation Callback method. (https://github.com/esri/arcgis-pro-sdk/wiki/ProConcepts-Editing#editoperation-callback) This choice (between coarse-grained edit operation methods and the callback method) is mutually exclusive. That is, you either invoke the callback method or coarse grained operation methods (using whichever combination of Create, Modify, Cut, etc. methods are desired) but not both. So, the fix then, is to change the code to use either the callback or the create. To use the callback approach, replace the code inside "rowCursor.MoveNext()" with a block of code that looks something like this (pulled from this snippet https://github.com/esri/arcgis-pro-sdk/wiki/ProSnippets-Geodatabase#creating-a-row). Notice use of RowBuffer.CreateRowBuffer and Table.CreateRow to do the create and not the editoperation.Create. using (RowBuffer rowBuffer = enterpriseTable.CreateRowBuffer())           {     // Either the field index or the field name can be used in the indexer.     rowBuffer[assetNameIndex] = "wMain";                 rowBuffer["COST"] = 700;                 rowBuffer["ACTION"] = "Open Cut";    // subtype value for "Abandon".                rowBuffer[tableDefinition.GetSubtypeField()] = 3;                  using (Row row = enterpriseTable.CreateRow(rowBuffer))                 {                      // To Indicate that the attribute table has to be updated.                     context.Invalidate(row);                  }           } To use editoperation.create, delete the enclosing callback statement which should leave your existing code relatively intact (from "if (parcelShapes != null) down) looking something like this (pulled from this snippet https://github.com/esri/arcgis-pro-sdk/wiki/ProSnippets-Editing#edit-operation-create-features) //Do your loop here.... while(rowCursor.MoveNext()) {   //then inside the loop...   //Do a create features and set attributes   var attributes = new Dictionary<string, object>();   attributes.Add("SHAPE", polygon);   attributes.Add("NAME", "Corner Market");   attributes.Add("SIZE", 1200.5);   attributes.Add("DESCRIPTION", "Corner Market");   createFeatures.Create(featureLayer, attributes); } //exit the loop //Call this when you are all done with the loop //FYI: should be no need to use the editOperation.ExecuteAsync flavor editOperation.Execute(); Use of the editOperation.Create would be the preferred approach (unless you have non-GIS data) and it is typically an easier pattern to implement. ... View more