Warnings

This section provides general information about some elements and objects that can be imported using the Design Import tool.

Design Import Restrictions

• Currently, the design upgrade file is created only for updating a TeamConnect instance design from an older design to newer design. If you need to revert a QA or production TeamConnect instance to an older design version, there are two possible methods:
  • If the older design version is captured in an earlier snapshot, use the method described in Reverting to a Previous Snapshot.
  • If there is no earlier snapshot, you must make the design changes manually on the development TeamConnect instance, take a snapshot of the current design, and create a corresponding design upgrade file.
• This release of the Design Import tool does not support importing user accounts.
• Deleting System Settings is not supported during importing.
• Please be aware that when you import specific object types, some child elements are deleted from the destination TeamConnect (QA or production) and replaced by the child elements from the source TeamConnect design (from the development instance).

Please see the following table for specific details:

Source Design With No Design Component

Generally, if the source design (from the development TeamConnect instance) does not include a design component (defined at the XML element level) and the destination design includes the corresponding design component, the import deletes that component from the destination TeamConnect database (for example, QA or production TeamConnect).

For example, if a Dispute object definition is being imported and the source XML file contains definitions for four phases, and the destination XML file contains definitions for five phases (including the four phases from the source database plus an additional phase), the import results in the deletion of the unique phase from the TeamConnect destination database.

This deletion would appear in the log file, but that log entry is not tagged with any specific error message.

General Troubleshooting Steps

This section provides a general flow for locating the source of DMT issues within a design "diff." In addition, a few examples of errors you could find in the DMT log file and troubleshooting tips are provided.

1. Click the View Log link to open the dmt.log file.
2. If a DMT operation is successful, the last line of the log file will contain a success message. Otherwise, the end of the log file will contain a message that the operation failed, followed by detailed messages about each error.
3. Search for "FATAL" in the log to find issues that must be resolved for the import (or snapshot creation or upgrade file generation) to complete.
4. Afterward, search for "ERROR" in the log for additional issues.

Sample Error Messages and Tips

The following are examples of error messages you might find in the log file. Specific details may differ for your designs/diffs but you can apply these to troubleshooting concepts for your specific scenarios.

• Error message:
  FATAL - ImExCustomLookupTables.import: caused exception importing custom lookup table=LOOK1UP.xml com.mitratech.teamconnect.foundation.TCException: Cannot delete YDetailLookupItem because it still has 4 EProjDetailObjeValues referencing it
  1. To locate the corresponding *.XML source file, from your diff path, navigate to:
     diff\Lookup Tables\Custom\I.xml
     where diff is the path to the diff
     If the issue were in a system lookup table, you could find the *.XML file in diff\Lookup Tables\System\LOOK1UP.xml
  2. If you open the source *.XML file, the first line should end like:
     "opcode="delete"
     This is the command that tries to delete lookup table items.
  3. It is recommended to rename the *.XML file (like *.XML.old) so the DMT will skip the file during import but you can later track changes that might need to be made manually.
• Error message:
  FATAL - ImExCategory.import: exception unmarshalling.Please enter a unique name.
com.mitratech.teamconnect.foundation.TCException: Please enter a unique name.
  1. To locate the corresponding *.XML source file, look in the dmt.log file at the events just above (before) the FATAL message. A sample excerpt follows:
     DEBUG - ImExCategory.importCategory: key=OTHE
DEBUG - ImExCategory.importCategory: itemKey=PR01_OTHE, opCode=insert
DEBUG - ImExCategory.importCategory: inserting category for itemKey=PR01_OTHE, parent=PR01
DEBUG - ImExCategory.importCategory: inserting category for itemName=OTHER, key=OTHE, order=0
  2. The first four characters of the itemKey, PRO1_OTHE, or PRO1, indicates the object for which a duplicate category was found.
  3. From your diff path, navigate to:
     diff\Object Definitions\PRO1\categories.xml
     where diff is the path to the diff
  4. Open the categories.xml file and search for "PR01_OTHE" For example, the context could look like:
     <Category displayOrder="" name="Other" treePosition="PR01_OTHE" isActive="true" opcode="insert" />
  5. Generally you must verify that you do not create a category that already exists in the target instance. It is recommended to comment out the corresponding line from the categories.xml file so DMT will skip insertion of the duplicate category.
• Error message:
  FATAL - ImExCustomFields.import: caused exception for filename=PR01_0112.xml com.mitratech.teamconnect.foundation.TCException: Cannot delete Detail Field because it still has 1 EProjDetailTextValue referencing it
  1. To locate the corresponding *.XML source file, from your diff path, navigate to:
     diff\Object Definitions\PRO1\Custom Fields\PR01_0112.xml
     where diff is the path to the diff
  2. If you open the source *.XML file, the first line should end like:
     opcode="delete"
     This is the command that tries to delete the detail field.
  3. It is recommended to rename the *.XML file like *.XML.old so the DMT will skip the file during import but you can track changes that might need to be made manually.

Error Messages and Performance Issues

This section contains some limitations in the Design Snapshot tool or Design Import tool. For most of these issues, workarounds are provided. If a workaround is not provided and you need more information, please contact Mitratech support.

• BUILD FAILED message
• DMT script errors