Identifying Conflicts That Occur During Upgrades

This topic describes how to identify merge conflicts between objects that are added or modified during a repository merge. A merge conflict is a scenario in which a customer changed an object in the current customer repository and Siebel CRM changed that same object to a different value in a new version of the Siebel Repository. Consequently, the attribute for the object is different when the following three repositories are compared: the current customer repository, the current Siebel Repository, and the new version of the Siebel Repository.

To identify conflicts that occur during upgrades (Siebel Tools)

1. Make sure you finish upgrading repositories.

   For more information, see Upgrading Repositories.

2. Click the Screens menu, click Application Upgrader, and then click Application Upgrade Object List.

3. In the Application Upgrades list, right-click the record of the merge that you want to analyze, and then click Hierarchy Reports.

   The hierarchy report appears, which includes the objects that were added or modified during a merge. The report includes the following types of objects:

   • Objects that include a valid value for each field value. These objects were modified during the merge. An N or a Y in a binary field is an example of a valid value.

     For these objects, the Status field designates added objects or objects with modified attributes. For added objects, an N appears in the Attributes field because none of the attributes are modified. For objects with modified attributes, a Y appears in the Attributes field, and the modified attributes appear in the Attributes pane.

   • Objects that include an asterisk (*) for each field value. Children of these objects were modified during the merge, or the dependent objects of these objects were modified during the merge.

4. To view information about merge details, complete the following steps:

   1. Expand the (Object Types) hierarchical tree and select a parent or child object type.

   2. Select an object in the List of Objects list.

      In the Attributes pane, the merge conflicts for the selected object are listed.

5. (Optional) To filter the objects in the report, select one of the following values in the Filter drop-down list, and then click Go:

   • Siebel and Customer Modified. Displays only objects that Oracle or you modified. These objects have a Y in the In Prior Standard, In Prior Customized, and In New Standard fields.

   • Siebel Modified. Displays only objects that Oracle modified or added. These objects have an N in the In Prior Standard and In Prior Customized field and a Y in the In New Standard field.

   • All. Displays all modified or added objects.

6. (Optional) To filter the merge conflicts in the Attributes pane, select or clear the Critical Only check box as follows, and then click Go:

   • Select the check box to show only critical merge conflicts.

   • Clear the check box to show all merge conflicts.

7. (Optional) To display the dependencies for an object, complete the following steps:

   1. Click an object in a List of Objects pane.

      If you want to display the dependencies for an additional object, then hold down the CTRL key, and click the additional object in the List of Objects pane.

   2. Click Show Dependencies (if the object has no dependencies, then the Show Dependencies button is disabled).

      The dependent objects that were modified are displayed and the attributes for these objects.

   3. Click Back to return to the hierarchy report.