Creating versions in a geodatabase allows you parallel and secured processing of that same database by different users at the same time. This means that no data has to be locked or duplicated. Each version has a dedicated owner, ensuring clear responsibility and edit tracking. This setup supports long transactions by allowing editors to work independently in their own version over extended periods. After editing, the versions are compared with the parent version (default version) and written back to it.

You can find an overview of versioning on the Esri homepage.

To create a new version:

1.Go to Edit > Versions.
The Versions panel opens and a list of saved versions is shown.
The following tools are available in the opened panel:

The filter functions can be combined with each other. Their mode of operation behaves additively.

You can navigate between the versions displayed in the list using the arrow keys.
A selected version can be opened with the ENTER key.

2.Create a new version by clicking on the Create button.
The create version window appears as follows:

3.Fill in the required parameters, the access permissions can be described as follows:

Then, press Finish.
Your new version is created and switched to, and displayed by name at the bottom of the page, highlighted with a green bar.

If no version is selected, the Default version is displayed.
Users with administrator privileges can perform all actions on any version.
The creation date of the version is assigned automatically.
You can switch to this editing version for immediate editing by ticking the "Switch to version" check-box when creating. In addition, you can switch between versions by clicking on a version in the list or via the action menu of the version.

4.Create or edit feature(s) in an edit version.
Your new changes are saved in the edit version.

The editing options of the versions depend on the access permissions.

5.Save your edits by either reconciling or posting changes.
 
Reconcile changes
Reconciliation aligns your editing version with the current state of the default version. Any changes made to the default version since your edits began are brought into the editing version. If both versions modified the same features, conflicts are detected, and a warning prompts you to either:

•Resolve conflicts in favor of the editing version.

•Abort the process to prevent overwriting changes from the default version.

In the Network Editor, conflicts are always resolved in favor of the editing version. In case of ambiguity, a more differentiated conflict resolution must be performed via ArcGIS Pro.

Reconciliation can be skipped if you intend to Post changes directly.

 
Post changes
Posting writes all edits from the editing version back to the default version. Before posting, the the system automatically performs a reconciliation and transfers any default version changes to the editing version. If no conflicts are found, the edits are posted. In the event of a conflict, a warning appears. You can either:

•Resolve conflicts in favor of the editing version and proceed.

•Cancel and resolve the conflicts manually in ArcGIS Pro before posting.

6.Delete the version after it is no longer needed.

 

Release Lock

The Networks Editor automatically locks a version when it is opened by a specific user session. This ensures that only one user can edit a given version at a time, preventing conflicts and maintaining data integrity. To manually release the lock, use the Release Lock option from the action menu.

Releasing the lock will discard any unsaved edits made during the current session.

Functions of the action menu

The following helpful functions are available via the action menu next to the displayed version:

Markups and Hints are not connected to a geodatabase version.

For a space-saving view, the compact view can be selected in the "Status bar" section.