I have a set of tasks I use for guiding folks with a very wide range of skill levels through a series of quarterly update processes in Pro. The single biggest pain point is saving edits. If users make edits early in the task and do not save them, it will lead to bad data and errors later in the process. I can call the Save Edits command as a task step, but if there are no pending edits when the call is made (which happens ~50% of the time) the command generates an error and convinces the same new / low expertise users that perennially fail to save their edits that the whole thing broke.
So, what I would like to propose is either:
- A Save Edits command that can fail silently if no edits are pending, thereby allowing me to call it in a hidden and auto-proceeding step. Or, even better
- The ability to call the Save Edits command via arcpy, allowing me to wrap it in a try/except to suppress the error message when I want to without changing the existing functionality of the command itself.
Worth noting: I have mucked around with trying to hard-force a save with a stopEditing call and so far as I can tell it is not a feasible solution.
