There are three types of conflicts that can occur during the upgrade:
•Manual Conflicts—These are conflicts that must be resolved outside of Upgrade Toolkit before you can initiate the installation process.
•Automatic Conflicts—These are conflicts that will be automatically handled by Upgrade Toolkit during the installation process.
•Selection Conflicts—These are conflicts that can be resolved within Upgrade Toolkit, and require the user's input on which action to take per each incidence of selection conflict.
Further details on each individual conflict can be found in the Conflict Report, which can be exported from the Conflict Checking - Summary screen.
Manual Conflicts
Manual conflicts cannot be resolved by Upgrade Toolkit, and must be dealt with either in the TeamConnect instance or directly in its database. There are two main methods for resolving these conflicts, described as follows.
•From within TeamConnect, make a copy of the affected object, then alter the dependent data so that it does not reference the original affected object and instead references the copy of the affected object. Then delete the original affected object.
•From within the instance's database, remove the dependency between the affected object and its dependent data for each affected object. In most cases, this will involve altering an attribute of the affected object. Take care to not edit the primary key of the affected object.
Important: For any manual conflict, only one of the previously described resolutions is necessary. Do not perform both resolutions on one conflict.
See Manual Conflict Examples for examples of manual conflicts and the steps required to resolve them.
Automatic Conflicts
These conflicts are automatically resolved by Upgrade Toolkit. The action that will be taken on each object is listed in the Instructions column of the Conflict Report. If you do not want the automatic conflict resolution to occur, you must exit Upgrade Toolkit before initiating the installation process and take action on the object from within TeamConnect.
The three types of Automatic Conflicts and their resolutions are described below.
•Delete-Delete—For this type of conflict, Upgrade Toolkit will leave the previously deleted object deleted.
•Insert-Insert—For this type of conflict, Upgrade Toolkit will automatically delete the existing object and insert the upgrade version of the object.
•Delete-Update—For this type of conflict, Upgrade Toolkit will automatically delete the existing updated object.
Note: There is one automatic conflict that always appears in upgrades from version TeamConnect Legal Matter Management 3.0 SP1, on the {folder=System/Libraries, name=legal-legalutilities-library-3.0.0.0055.jar} Document. This object is modified by the upgrade of TeamConnect Enterprise, and is not actually a conflict.
Selection Conflicts
There are two types of Selection Conflicts. In each case, you will be given the option of two different actions to take: the first option (Upgrade Action) is to accept the upgrade resolution, while the second option (Client Action) is to retain the current state of the object.
The two types of Selection Conflicts are described below.
•Update-Delete—This type of conflict occurs when objects were previously removed in the client instance, and the upgrade process calls for updating them.
oNote: Update-Delete conflicts involving wizards, rules, or line item categories are automatically resolved. The reinsert option (Upgrade Action) is not available for these objects.
•Update-Update—This type of conflict occurs when objects were previously modified in the client instance, and the upgrade process calls for different modifications.
Important: It is recommended that you select the Upgrade Action on all finance objects and objects if you are planning on installing TeamConnect Financial Management.
Important: In certain situations, selecting the Client Action for objects that are dependent on other conflict resolutions can cause the installation to fail. The imported data will be rolled back and the instance will be returned to its original state. The Import Log contains information that will pinpoint the dependencies that caused the failure. You must change your selections for these dependencies to match each other for the installation to succeed.
