Reconcile Express Design

An express design needs to be reconciled before it's posted. In short, this function looks for other changes that have been posted to the same parent version of your design (the parent version is almost always SDE.DEFAULT), and those changes are in conflict with your changes. This can happen when multiple editors are working on the same set of feature classes at the same time. If conflicts are surfaced, typically an administrator or senior designer chooses which representation of the conflicting feature classes are correct.

An express design may be reconciled any time after it has been created. Further, it may be reconciled multiple times. If you are using an Access database, no parent version exists. Therefore, the Reconcile button will remain disabled when you are working in a Access database.

Open the express design to be reconciled.
On the Designer Express Commissioning toolbar, click the Reconcile Design button.
You are prompted to define how to reconcile the design.
- The Target Version needs to be the same as what is configured in WMSDefaultParentVersion to ensure proper results. This is nearly always SDE.DEFAULT, but check with your administrator if you are unsure.
- Defining conflicts by object (by row) is the default. This means that when resolving conflicts, you accept changes for an entire row if there is any difference between the Target and Edit Versions. For example, imagine reconciling a change in a distribution main segment, and the following attributes are conflicting:
  - Distribution Main in your Edit Version:
    - Material: Steel
    - Diameter: 18”
    - Manufacturer: Steel Inc.
  - Distribution Main in the Target Version:
    - Material: Cast Iron
    - Diameter: 12”
    - Manufacturer: Metalworks Inc.
  Defining conflicts by object means you choose one of the above representations of the distribution main. You do not pick and choose among the three attributes, you accept one set or the other.
  
  Defining conflicts by attribute means you would be able to pick and choose which attributes to accept in the case of conflict.
- Resolving conflicts in favor of the Target Version is the default. Notably, edits are not inherently conflicts. Conflicts only arise when another design has been posted to the default ahead of yours that included changes to the same feature class or object table rows in your design. Because it is assumed the other conflicting design went through your company’s QA/QC rules prior to post, it is at least assumed to be correct in case of conflict.
Click OK.