Summary
Registers an enterprise, workgroup, or desktop geodatabase dataset as versioned.
Usage
Versioning tools only work with datasets in an enterprise, workgroup, or desktop geodatabase. File and personal geodatabases don't support versioning.
Registering a feature dataset as versioned registers all feature classes within the feature dataset as versioned.
Versions are not affected by changes occurring in other versions of the geodatabase.
Archive-enabled datasets cannot be registered as versioned. If you've already enabled archiving on your data but you also want to register your data as versioned, you must first disable archiving, register the data as versioned, and re-enable archiving. You can enable archiving on versioned data, but you cannot register archived data as versioned.
Syntax
RegisterAsVersioned(in_dataset, {edit_to_base})
Parameter | Explanation | Data Type |
in_dataset | The dataset to be registered as versioned. | Table View; Feature Dataset |
edit_to_base (Optional) | Determines whether edits to the default version will be moved to the base tables.
| Boolean |
Derived Output
Name | Explanation | Data Type |
out_dataset | The updated input dataset. | Table View; Feature Dataset |
Code sample
RegisterAsVersioned example (stand-alone script)
The following stand-alone script demonstrates how to use the RegisterAsVersioned tool to register a dataset as versioned.
# Name: RegisterAsVersioned_Example.py
# Description: Registers dataset as versioned
# Import system modules
import arcpy
# Set local variables
datasetName = "c:/Connections/ninefour@gdb.sde/ninefour.GDB.ctgFuseFeature"
# Execute RegisterAsVersioned
arcpy.RegisterAsVersioned_management(datasetName, "NO_EDITS_TO_BASE")
Environments
Licensing information
- Basic: No
- Standard: Yes
- Advanced: Yes