Siebel Database Upgrade Guide > Performing the Siebel Incremental Repository Merge > Process of Upgrading the Siebel Development Environment from Siebel CRM Version 8.1.1.x (SIA Repository) >

Reviewing Siebel Repository Object Property Conflicts

This task is a step in Process of Upgrading the Siebel Development Environment from Siebel CRM Version 8.1.1.x (SIA Repository). Use the following task to review Siebel Repository object property conflicts.

Environments: Development environment only.

Platforms: Windows, UNIX, and IBM z/OS.

You can change how repository object property conflicts are resolved during the repository merge.

How Repository Object Property Conflicts Occur

NOTE:  Use the Hierarchical Reports feature in Siebel Tools to learn what conflicts might have occurred, and to help identify areas to target for regression testing. For more information on this feature, see Using Siebel Tools.

You cannot resolve conflicts from the report, but you can use the report to identify where to target regression testing and what conflicts have occurred.

The repository merge compares repository object properties in the Prior Siebel Repository, Prior Customer Repository, and New Siebel Repository. When the value of an object property is different in all three repositories, an object property conflict exists. This conflict occurs when you have changed the value of an object property in the Prior Customer Repository, and the value of this property has also changed in the new release (New Siebel Repository).

An object property conflict does not occur if you changed the value of an object property in the Prior Customer Repository, and the object property value did not change in the new release. When a conflict does not happen, the merge process transfers the changed value to the New Customer Repository.

The merge process resolves object property conflicts by referring to the setting of the object's Standard Win property. For the majority of repository objects, the merge process resolves conflicts by using the object property value in the New Siebel Repository.

Do not change the setting of the Standard Win property.

Reviewing Object Property Conflicts

You can review and change how object property conflicts were resolved using the Application Upgrade Attribute List view in Siebel Tools. The Attribute Differences List in the view includes the following columns:

• Object Name. The name of the object.
• Attribute. The object property name.
• Conflict. The merge process puts a check mark in this field if there was an object property conflict during the merge.
• Resolution. Displays which property value the merge process used to resolve the conflict:
  • Standard Value. The property value in the New Siebel Repository was used. This value is displayed in the New Standard column.
  • Custom Value. The property value in the Prior Customer Repository was used. This value is displayed in the Prior Customized column.
• Override. Puts a check mark in this column to change how the conflict is resolved. Overriding the resolution changes the property value in the merged repository. If the resolution was the Standard Value, then the displayed value is changed to the Custom Value and vice versa.

  Putting a check mark in the Override column does not change the value displayed in the Resolution column. A check mark indicates that the displayed value was manually overridden in the merged repository.

• Prior Standard. Displays the value of the object property in the Prior Siebel Repository.
• Prior Customized. Displays the value of the object property in the Prior Customer Repository. In the Resolution column, this value is called the Custom Value.
• New Standard. Displays the value of the object property in the New Siebel Repository. In the Resolution column, this value is called the Standard Value.
• Conflict Resolution Type. Displays whether the conflict is critical or non-critical. Only critical conflicts have to be resolved.