Editing Events with Enterprise Geodatabase

[JoePolaski]

I have an add in that had been previously working fine with a file geodatabase. Now I need to make it work with an enterprise geodatabase using no versioning. I noticed some significant changes to editing.

1. It seems that editing was automatically toggled when I was using a FGDB now it does not. Is this normal? If So how can I best overcome this ? For now I have manually toggled it.

2. Since there is no versioning I assume I am editing the default version. The save and discard buttons are always disabled. Is this because I am editing the default version and the changes cannot be undone ?

3. No edit events seem to be firing anymore (even with editing toggled on manually) and I have many custom event listeners that now seem to be broken. These events include RowCreatedEvent, RowChangedEvent and EditCompleted event. Is this normal behavior with an enterprise geodatabase ? Is there some way to track these events ?

Any clarification on these items would be very helpful. I didn't realize editing events and workflows would be so vastly changed by this migration to using an enterprise GDB. Does anyone have any advice or experience the same issue? Thanks in advance

[JoePolaski · Accepted solution]

So after more research and testing I have learned that in an enterprise geodatabase while editing a non-versioned feature class RowCreatedEvent, RowChangedEvent and EditCompleted events will not trigger. Also the discard and save buttons will be permanently disabled. Which after thinking about this more, kind of makes sense since you won't have the add and delete tables. Registering the feature class as versioned fixed this issue.