Scenario Overview:

Five feature classes are added to afeature dataset, which is registered as versionedwithout the move-edits-to-base option.

Afterward, another feature class is added to the same feature dataset.

Users encounter errors when trying to edit any feature class in the feature dataset.

Cause of the Problem:When a feature dataset is registered as versioned, all feature classes within it must maintain consistency in their versioning state. Adding a new feature class to a previously versioned feature dataset can disrupt the synchronization, causing errors during editing.

Solution:

Unregister as versioned on the feature dataset:This removes versioning from all feature classes in the dataset, resetting their versioning state.

Register the feature dataset as versioned again:This ensures all feature classes, including the newly added one, are correctly registered with the same versioning state.(ArcGIS Documentation: Registering Datasets as Versioned)

Alternative Options:

Option B:Registering the feature dataset again would not resolve the issue because versioning conflicts persist unless the entire feature dataset is unregistered and re-registered.

Option C:Switching to the move-edits-to-base option is unnecessary and alters the editing workflow, which may not align with the current setup or user needs.

Thus, the administrator shouldunregister the feature dataset as versioned and re-register itto resolve the errors.