ArcGIS Enterprise: Update table row failed. The object cannot be edited using the current edit session mode

Error Message

When editing feature classes within a feature dataset in an enterprise geodatabase (for example, modifying fields in the attribute table), the following error message is returned:

Error:
Update table row failed.
The object cannot be edited using the current edit session mode.

Cause

This issue occurs when a feature dataset registered as versioned contains one or more feature classes that are not versioned. All feature classes within a feature dataset must share the same versioning type. When the versioning states do not match, editing operations fail and the error is returned.

Solution or Workaround

To resolve the error, add or edit a nonversioned feature class in a versioned feature dataset.

1. Backup the database.
   1. Create a full, up-to-date backup of the enterprise geodatabase using the appropriate administration tool for the database platform (for example, SQL Server Management Studio for SQL Server). Refer to Portal for ArcGIS: Back up and restore best practices for more information.
2. Reconcile and post edits.
   1. In ArcGIS Pro, run Reconcile and Post on the feature dataset to move all edits to the default version. This step applies to both traditional and branch versioning. Refer to ArcGIS Pro: Reconcile and post edits to a branch version or ArcGIS Pro: Reconcile and post edits to a traditional version for instructions.

Note:
For traditional versioned feature datasets, proceed with Step 3. For branch versioned feature datasets, skip to Step 5.
The Compress operation applies only to traditional versioning. Branch versioning does not use delta tables and therefore does not require or support Compress.

3. Connect to the geodatabase (traditional versioning only).
   1. Create a geodatabase connection to the same enterprise geodatabase. This connection is used for the Compress operation.
4. Compress the geodatabase (traditional versioning only).
   1. Run the Compress geoprocessing tool.
   2. Verify that the compress operation is completed successfully using the database's available administrative tools. For example, in SQL Server, review the compress_log table. The operation is successful when end_state = 1, indicating that edits have been moved to the base table.
5. Unregister the versioned feature dataset.
   1. Connect to the enterprise geodatabase as the data owner and run the Unregister As Versioned tool on the feature dataset.

Warning:
• For traditional versioning, unregistering deletes the delta tables related to this feature dataset, so completing the Reconcile, Post, and Compress steps beforehand is essential.
• For branch versioning, ensure all named versions are reconciled and posted before unregistering to prevent loss of unposted edits.

6. Re-register the feature dataset as versioned (traditional or branch) to ensure all feature classes within the feature dataset are registered with the selected versioning type. Refer to ArcGIS Pro: Register As Versioned (Data Management) for more information.