Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Resolving conflicts in the Merge Branches wizard

Updated on April 5, 2022

To resolve the conflicts for a rule, complete the following steps:

  1. Examine the conflicts reported for the rule in the Conflicts and Warnings window.
  2. Click Compare next to the first conflict to examine the differences between your branch copy of the rule and the one in the base ruleset. Alternatively, click the ruleset name to open the base rule and directly examine it.
  3. Review and resolve all of the differences between the base rule and your branch rule.
    • If the changes are minor (such as a typo), open your branch rule and apply the same changes to it so that it matches the base rule.
    • If the changes are more complex, or if they conflict with the choices or logic in your branch rule, contact the individual who modified the base rule and negotiate what the final set of changes should be and the testing procedure for testing them. After reaching a mutual decision, make the agreed-upon changes in your branch rule and test.
  4. When changes to your branch rule are completed and tested, select the Mark as Resolved check box to indicate you have resolved the conflict.

After all conflicts reported in the Conflicts and Warnings window are marked resolved, you can click OK to close the window and return to the Merge Branches wizard to continue with the merge process.

In the main screen of the wizard, you can see if all conflicts are resolved by verifying if the number of Resolved conflicts matches the number of reported conflicts for all of the branch rulesets.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us