Hi Karen,
Can you perhaps answer a few questions about your scenario to help us track this problem down. I am currently unable to reproduce on 2.8 final, 2.8.1 or even our current build.
- Are you using file geodatabase or enterprise data? If enterprise, what database platform (Oracle, SQL etc)
- What overload of EditOperation.Modify are you using? Are you modifying geometry or attributes or geometry and attributes. I tested using this overload passing only the layer, oid and geometry (No attributes).
public void Modify(Layer layer, long oid, Geometry geometry, Dictionary<string, object> attributes = null);
- Is there anything special about your data; ie does it participate in a topology, utility network etc? I was just using a polygon layer inserted via Map Notes.
- I was using France as my region ensuring that the decimal separator was the comma. Can you duplicate the problem with many different regions that use the comma as the decimal separator?
- Finally, maybe this is obvious, but have you verified via the debugger that the new geometry shape is a non empty geometry before passing it to EditOperation.Modify? (https://pro.arcgis.com/en/pro-app/latest/sdk/api-reference/#topic8175.html)
Thanks for any answers you can provide.
Narelle