The reconcile process requires that you are the only user currently editing the version and the only user able to edit the version throughout the reconcile process until you save or post.
The reconcile process requires that you have full permissions to all the feature classes that have been modified in the version being edited.
Versioning tools only work with ArcGIS enterprise data. File and geodatabases don't support versioning.
The geodatabase is designed to efficiently manage and support long transactions using versions.
The reconcile process detects differences between the edit version and the target version and flags these differences as conflicts. If conflicts exist, they should be resolved.
The enterprise geodatabase containing the reconcilable version.
Workspace
Version Name
Name of the Edit Version to be reconciled with the Target Version.
String
Target Version
Name of any version in the direct ancestry of the Edit version, such as the parent version or the default version.
String
Conflict Definition
(Optional)
Describes the conditions required for a conflict to occur:
Checked—Any changes to the same row or feature in the parent and child versions will conflict during reconcile. This is the default.
Unchecked—Only changes to the same attribute of the same row or feature in the parent and child versions will be flagged as a conflict during reconcile. Changes to different attributes will not be considered a conflict during reconcile.
BY_OBJECT—Any changes to the same row or feature in the parent and child versions will conflict during reconcile. This is the default.
BY_ATTRIBUTE—Only changes to the same attribute of the same row or feature in the parent and child versions will be flagged as a conflict during reconcile. Changes to different attributes will not be considered a conflict during reconcile.
String
Conflict Resolution
(Optional)
Describes the behavior if a conflict is detected:
Checked—For all conflicts, resolves in favor of the target version. This is the default.
Unchecked—For all conflicts, resolves in favor of the edit version.
FAVOR_TARGET_VERSION—For all conflicts, resolves in favor of the target version. This is the default.
FAVOR_EDIT_VERSION—For all conflicts, resolves in favor of the edit version.
String
Acquire locks during reconcile
(Optional)
Determines whether feature locks will be acquired.
Checked—Acquires locks when there is no intention of posting the edit session. This is the default.
Unchecked—No locks are acquired and the edit session will be posted to the target version.
Boolean
Abort if conflicts
(Optional)
Determines if the reconcile process should be aborted if conflicts are found between the target version and the edit version.
Checked—Aborts the reconcile if conflicts are found.
Unchecked—Does not abort the reconcile if conflicts are found. This is the default.
Boolean
Post version after reconcile
(Optional)
Posts the current edit session to the reconciled target version.
Checked—Current edits will be posted to the target version after the reconcile.
Unchecked—Current edits will not be posted to the target version after the reconcile. This is the default.
The enterprise geodatabase containing the reconcilable version. The default is to use the workspace defined in the environment.
Workspace
version_name
Name of the Edit Version to be reconciled with the Target Version.
String
target_name
Name of any version in the direct ancestry of the Edit version, such as the parent version or the default version.
String
conflict_definition
(Optional)
Describes the conditions required for a conflict to occur:
BY_OBJECT—Any changes to the same row or feature in the parent and child versions will conflict during reconcile. This is the default.
BY_ATTRIBUTE—Only changes to the same attribute of the same row or feature in the parent and child versions will be flagged as a conflict during reconcile. Changes to different attributes will not be considered a conflict during reconcile.
String
conflict_resolution
(Optional)
Describes the behavior if a conflict is detected:
FAVOR_TARGET_VERSION—For all conflicts, resolves in favor of the target version. This is the default.
FAVOR_EDIT_VERSION—For all conflicts, resolves in favor of the edit version.
String
aquired_locks
(Optional)
Determines whether feature locks will be acquired.
LOCK_ACQUIRED—Acquires locks when there is no intention of posting the edit session. This is the default.
NO_LOCK_ACQUIRED—No locks are acquired and the edit session will be posted to the target version.
Boolean
abort_if_conflicts
(Optional)
Determines if the reconcile process should be aborted if conflicts are found between the target version and the edit version.
ABORT_CONFLICTS—Aborts the reconcile if conflicts are found.
NO_ABORT—Does not abort the reconcile if conflicts are found. This is the default.
Boolean
post
(Optional)
Posts the current edit session to the reconciled target version.
POST—Current edits will be posted to the target version after the reconcile.
NO_POST—Current edits will not be posted to the target version after the reconcile. This is the default.
Boolean
Derived output
Name
Explanation
Data type
out_workspace
The updated workspace.
Workspace
Code sample
ReconcileVersion example (stand-alone script)
The following stand-alone Python script uses the ReconcileVersion function to reconcile a version with a version in the version's lineage and then posts that version.
# Description: Reconciles a version with a version in the version lineage and
# then posts that version.
# Import system modules
import arcpy
# Set local variables
inWorkspace = "Database Connections/ninefour@gdb.sde"
versionName = "myVersion"
targetVersion = "dbo.DEFAULT"
# Run ReconcileVersion
arcpy.management.ReconcileVersion(inWorkspace, versionName, targetVersion, "BY_OBJECT",
"FAVOR_TARGET_VERSION", "LOCK_acquireD", "NO_ABORT",
"POST")