Show Navigation | Hide Navigation
You are here:
Geoprocessing tool reference > Data Management toolbox > Versions toolset > Tools

Reconcile Version (Data Management) (ArcInfo and ArcEditor only)

Release 9.2
Last modified November 29, 2010		 E-mail This Topic Printable Version Give Us Feedback

Print all topics in : "Tools"


Related Topics

Reconciles a version against a parent version in its lineage.

Reconcile merges all modifications between the current edit version and a target version. Any differences between the features in the target version and the features in the edit version are applied to the edit version. Differences can consist of newly inserted, deleted, or updated features. The reconcile process detects these differences and discovers any conflicts. Reconciling happens before posting a version to a target version. A target version is any version in the direct ancestry of the version, such as the parent version or the default version.


Usage tips

Command line syntax
An overview of the Command Line window
ReconcileVersion_management <in_workspace> <version_name> <target_name> {BY_OBJECT | BY_ATTRIBUTE} {FAVOR_TARGET_VERSION | FAVOR_EDIT_VERSION} {LOCK_AQUIRED | NO_LOCK_AQUIRED} {NO_ABORT | ABORT_CONFLICTS} {NO_POST | POST}

Parameter Explanation Data Type
<in_workspace>

The ArcSDE geodatabase containing the reconcilable version. The default is to use the workspace defined in the environment.

 Workspace
<version_name>

Name of version to be reconciled.

 String
<target_name>

Name of any version in the direct ancestry of the version, such as the parent version or the default version.

 String
{BY_OBJECT | BY_ATTRIBUTE}

Describes the conditions required for a conflict to occur:

  • BY_OBJECT — Any changes to the same object in the parent and child versions will conflict during reconcile. This is the default.

  • BY_ATTRIBUTE — sdsdChanges to the same attribute of the same object in the parent and child versions will be an update-update conflict during reconcile. Changes to different attributes will not be an update-update conflict during reconcile.

 String
{FAVOR_TARGET_VERSION | FAVOR_EDIT_VERSION}

Describes the behavior if a conflict is detected:

  • FAVOR_TARGET_VERSION — For all conflicts, resolve in favor of the target version. This is the default.

  • FAVOR_EDIT_VERSION — For all conflicts, resolve in favor of the edit version.

 String
{LOCK_AQUIRED | NO_LOCK_AQUIRED}

Determines whether feature locks will be aquired.

  • LOCK_AQUIRED — Aquires locks when there is no intention of posting the edit session. This is the default.

  • NO_LOCK_AQUIRED — No locks are aquired and the edit session will be posted to the target version.

 Boolean
{NO_ABORT | ABORT_CONFLICTS}

Determine if the reconcile process should be aborted if conflicts are found between the target version and the edit version.

  • NO_ABORT — Do not abort the reconcile if conflicts are found. This is the default.

  • ABORT_CONFLICTS — Abort the reconcile if conflicts are found.

Boolean
{NO_POST | POST}

Posts the current edit session to the reconciled target version.

  • NO_POST — Current edits will not be posted. This is the default.

  • POST — Current edits will be posted.

 Boolean
Data types for geoprocessing tool parameters


Command line example

reconcileversion_management  "Database Connections\Connection to workspace.sde" roads DEFAULT

Scripting syntax
About getting started with writing geoprocessing scripts
ReconcileVersion_management (in_workspace, version_name, target_name, conflict_definition, conflict_resolution, acquire_locks, abort_if_conflicts, post)

Parameter Explanation Data Type
in_workspace (Required)

The ArcSDE geodatabase containing the reconcilable version. The default is to use the workspace defined in the environment.

 Workspace
version_name (Required)

Name of version to be reconciled.

 String
target_name (Required)

Name of any version in the direct ancestry of the 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 object in the parent and child versions will conflict during reconcile. This is the default.

  • BY_ATTRIBUTE — sdsdChanges to the same attribute of the same object in the parent and child versions will be an update-update conflict during reconcile. Changes to different attributes will not be an update-update conflict during reconcile.

 String
conflict_resolution (Optional)

Describes the behavior if a conflict is detected:

  • FAVOR_TARGET_VERSION — For all conflicts, resolve in favor of the target version. This is the default.

  • FAVOR_EDIT_VERSION — For all conflicts, resolve in favor of the edit version.

 String
acquire_locks (Optional)

Determines whether feature locks will be aquired.

  • LOCK_AQUIRED — Aquires locks when there is no intention of posting the edit session. This is the default.

  • NO_LOCK_AQUIRED — No locks are aquired and the edit session will be posted to the target version.

 Boolean
abort_if_conflicts (Optional)

Determine if the reconcile process should be aborted if conflicts are found between the target version and the edit version.

  • NO_ABORT — Do not abort the reconcile if conflicts are found. This is the default.

  • ABORT_CONFLICTS — Abort the reconcile if conflicts are found.

Boolean
post (Optional)

Posts the current edit session to the reconciled target version.

  • NO_POST — Current edits will not be posted. This is the default.

  • POST — Current edits will be posted.

 Boolean

Data types for geoprocessing tool parameters


Script example

import arcgisscripting
gp = arcgisscripting.create()

gp.reconcileversion( "Database Connections\Connection to workspace.sde", "v1_vegetation", "DEFAULT")

Please visit the Feedback page to comment or give suggestions on ArcGIS Desktop Help.
Copyright © Environmental Systems Research Institute, Inc.