Synchronize Changes

A valid replica with a parent contained in one input geodatabase and a child in the other input geodatabase.

Specifies the direction in which the changes will be synchronized: from geodatabase 1 to geodatabase 2, from geodatabase 2 to geodatabase 1, or in both directions. For check-out/check-in replicas or one-way replicas, there is only one appropriate direction. If the replica is two-way, all of the choices are available.Both directions—Changes will be synchronized in both directions. This is the default.From geodatabase 2 to geodatabase 1—Changes will be synchronized from geodatabase 2 to geodatabase 1.From geodatabase 1 to geodatabase 2—Changes will be synchronized from geodatabase 1 to geodatabase 2.

Specifies how conflicts will be resolved when they are encountered.Manually resolve conflicts—Conflicts will be resolved manually in the versioning reconcile environment.Resolve in favor of geodatabase 1—Conflicts will be resolved in favor of geodatabase 1. This is the default.Resolve in favor of geodatabase 2—Conflicts will be resolved in favor of geodatabase 2.

Specifies how conflicts will be defined.Conflicts defined by row—Changes to the same row or feature in the parent and child versions will conflict during reconcile. This is the default.Conflicts defined by column— Only changes to the same attribute (column) 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.

Specifies whether to automatically reconcile once data changes are sent to the parent replica if there are no conflicts present. This option is only available for check-out/check-in replicas.Unchecked—Do not reconcile with the parent version. This is the default.Checked—Reconcile with the parent version.