To allow editors to see changes made to the default version in their child versions without reconciling, the dataset must be registered astraditional versioned with the option to move edits to base.

1. How This Versioning Method Works

When registering data astraditional versioned with the option to move edits to base, changes made in the default version are immediately visible to all child versions without requiring reconciliation.

This method directly updates the base table for default version edits, bypassing the delta tables used in standard traditional versioning workflows.

2. Why Use This Method?

Immediate Visibility: Editors can see default version updates in their child versions without the need for reconciliation or posting.

Simplified Workflow: Reduces the overhead of managing version reconciliation and posting for users who only need to view updates.

3. Why Not Other Options?

Branch Versioned with Global IDs and Editor Tracking Enabled:

Branch versioning is designed for feature services and web-based editing workflows. It does not allow direct visibility of default version changes in child versions.

Traditional Versioned with Archiving and Editor Tracking Enabled:

This method tracks historical changes but does not allow child versions to see updates in the default version without reconciliation.

Steps to Register Data with Move Edits to Base Option:

InArcGIS Pro, right-click the dataset or feature class and selectManage > Register as Versioned.

Check the option"Move edits to base"during registration.

Save the changes and verify that editors can view default version changes without reconciliation.

References from Esri Documentation and Learning Resources:

Traditional Versioning with Move Edits to Base

Versioning Options in Enterprise Geodatabases

Conclusion:

Registering the dataset astraditional versioned with the option to move edits to baseensures that editors can see changes made to the default version in their child versions without requiring reconciliation.