The Versions toolset contains tools to manage the versioning process.
Versioning allows multiple users to access geographic data in a geodatabase. This allows connected users to simultaneously create multiple, persistent representations of the geodatabase without data duplication. The same features or rows can be concurrently edited without explicitly locking the data. Using this framework you can create versions of a geodatabase for the states of a project, reconcile differences between versions, and update the default version of a geodatabase with the design as built. Versioning is supported by the enterprise geodatabase only.
An organization can use versioning to manage alternative engineering designs, solve complex what-if scenarios without impacting the corporate database, and create point-in-time representations of the database.
Versioning simplifies the editing process. Multiple users can directly modify the database without extracting data or locking features and rows before editing.
Tool | Description |
---|---|
Adds a field conflict filter for a given field in a geodatabase table or feature class. | |
Alters the properties of a geodatabase version. | |
Modifies the workspace of a layer or table view to connect to the specified version. | |
Creates a new version in a specified geodatabase or feature service. | |
Deletes the specified version from the input enterprise geodatabase. | |
Reconciles a version or multiple versions with a target version. | |
Registers an enterprise geodatabase dataset as versioned. | |
Removes a field conflict filter for a given field in a geodatabase table or feature class. | |
Unregisters an enterprise geodatabase dataset as versioned. |