The answer is because you are editing in a parcel fabric. When editing in a parcel fabric, the OnCreateFeature and OnChangeFeature events do not fire. No explanation is given in ESRI documentation for why this is the case, but I suspect that it has to do with parcels being edited through a job XML stream.
You aren't the only one to have this issue. See this mirror of a now-deleted (for inactivity) GIS.SE post of someone with the exact same issue.
No, setting CanBypassStoreMethod() does not fix the issue. Yes, this should be in ESRI's documentation somewhere that this event does not fire when working on cadastral/parcel fabrics, as well as some sort of workaround.
There are events available within the parcel table interfaces that fire when working within a parcel editing window (OnStartParcelEditing, OnJoin, job events, etc) but if someone edits an attribute table without opening this window, they will not fire. We want an event that fires if any changes are made to the attribute table whatsoever, so the aforementioned events do not fully encapsulate this action.
The answer is to get these changes from an edit operation. All ArcMap editor session edits are encapsulated in an edit operation. The events that fire whenever you add a feature or make an edit to the attribute table (from ESRI documentation) are as follows:
- OnStartOperation event fired
- OnChangeFeature/OnCreateFeature event fired
- BeforeStopOperation event fired
- OnStopOperation event fired
I discovered that in a parcel fabric, the OnChangeFeature (or OnCreateFeature if you are adding a parcel) does not fire, but the other three events do. So we can listen to BeforeStopOperation, which happens after the edit is complete but before the edit is saved. Wire your event handler for this, and also declare an IWorkspaceEdit2 for use later:
private IWorkspaceEdit2 WorkspaceEdit;
void Events_OnStartEditing()
{
if (ArcMap.Editor.EditWorkspace.Type !=
esriWorkspaceType.esriFileSystemWorkspace)
{
//wire BeforeStopOperation editing event
Events2.BeforeStopOperation += new IEditEvents2_BeforeStopOperationEventHandler
(Events2_BeforeStopOperation);
WorkspaceEdit = (IWorkspaceEdit2)ArcMap.Editor.EditWorkspace;
}
}
Now that we wired the event, whenever it fires we need to get the changes. In your OnStopOperation event get IDataChangesEx from your IWorkspaceEdit2. IDataChangesEx holds not only the changed objects from within the edit operation but other various objects that give you pretty much all the freedom you want to manipulate them:
void Events2_BeforeStopOperation()
{
IDataChangesEx dataChanges = WorkspaceEdit.get_EditDataChanges(esriEditDataChangesType.esriEditDataChangesWithinOperation);
ESRI.ArcGIS.esriSystem.IEnumBSTR classes = dataChanges.ModifiedClasses;
string changedClass = classes.Next();
MessageBox.Show(changedClass);
if (changedClass == "GISDEV.DBO.PARCELFABRIC_PARCELS")
{
if (ParcelTable == null)
{
ParcelTable = parcelGateway.get_ParcelTable(out ParcelTable);
}
parcelGateway.ValidateParcelAttributes(changedClass, dataChanges, ParcelTable);
}
This should work with both versioned and unversioned parcel fabrics.
One unexplainable issue I encountered in this implementation is that it does not work in file geodatabases. IWorkspaceEdit.get_Editdatachanges() was returning null. The code works just fine in an SDE environment, however.
Best Answer
You may need to get the dataset's name from the feature first. Then you can loop all the layers in TOC and check if their dataset name matches the one obtained earlier. It would look something like below.