This document is archived and information here might be outdated.  Recommended version.

IDataChangesEx Interface (ArcObjects .NET 10.8 SDK)
ArcObjects Help for .NET developers > ArcObjects Help for .NET developers > ArcObjects namespaces > Geodatabase > ESRI.ArcGIS.GeoDatabase > Interfaces > ID > IDataChangesEx Interface
ArcGIS Developer Help

IDataChangesEx Interface

Provides access to members that return information on data changes.

Product Availability

Available with ArcGIS Engine, ArcGIS Desktop, and ArcGIS Server.


Name Description
Read-only property ChangedIDs The IDs of rows that changed during the edit session.
Method Extract Get changed rows for a specific class.
Method ExtractEx Get changed rows for a specific class.
Read-only property ModifiedClasses The list of tables with edits.

Classes that implement IDataChangesEx

Classes Description


The IDataChangesEx interface can be used by application developers to find out what features have been changed with the scope of an edit session or edit operation. The changes returned from a IDataChangesEx object are only accurate to the time of object creation. This means that any edits made after a reference to the IDataChangesEx object will not be reflected when ChangedIDs, Extract, and ExtractEx members are called. To get the most up to date data changes call ModifiedClasses and then Extract or ExtractEx. It is important to keep in mind this has the effect of flushing the edits made within an edit session, giving the application the most recent view of the dataset.

When required to insert, update or delete objects it is strongly recommended the operation is performed using an edit session and within an edit operation. Although the modification can be performed without explicitly starting and stopping an edit operation, the resulting change will be non-deterministic in respect to which state of the database the operation is associated or even the possibility of encountering an error when the change can not be applied to an open state. For these reasons all edits should be performed within an edit operation. The scope of the data changes can not be guaranteed when the ChangedIDs, Extract, and ExtractEx members are called on an edit session with edits made outside of an edit operation.

IDataChangesEx should not be used with non-versioned edit sessions.