Data Management Capabilities > Using Packages to Import and Export Data for Offline Collaboration > Import Received Delivery > Reviewing a Received Delivery Import Log
Reviewing a Received Delivery Import Log
A received delivery import log file contains a large amount of data about what occurred during import. The information is divided into multiple columns. The following table provides a description of each column available in the import log file.
Column
Title
Description
A
Timestamp
The time at which the import action occurred.
B
Severity
The severity of the log event. Possible values include:
• Info: messages about the import
• Error: conditions that may cause the import to be unsuccessful
• Warning: unexpected situation that will not cause the import to be unsuccessful
• Debug: information that is only available when debugging is enabled
C
Thread-ID
The identity of the thread. This value is useful when dealing with imports that use multiple threads.
D
Operation 1
The import handler or class name that provided the logging information.
E
Operation 2
The name of the operation that caused the log event.
F
Operation 3
Additional information about the log event, if any.
G
Operation 4
Additional information about the log event, if any.
H
Operation 5
Additional information about the log event, if any.
I
Message ID
The message type of the log event.
J
Message-Value
The log event message.
You can use a program such as Microsoft Excel to filter the data in the log file to show only the information that you need. The following sections provide tips on how to apply these filters.
Reviewing Import Errors
To review errors generated during received delivery import, add filters to the log file and filter on the ERROR value in the SEVERITY column. The OPERATION1 and OPERATION2 values show where the error is occurring.
Reviewing Import Warnings
To review warnings generated during received delivery import, add filters to the log file and filter on the WARNING value in the SEVERITY column. The OPERATION1 and OPERATION2 values show where the warning is occurring.
Reviewing Imported Objects
A list of objects that were imported is included in the import log file. You can display only the imported objects by adding filters to the log file and filtering on the importObject value in the OPERATION2 column. The object identities and names are displayed in the MESSAGE-VALUE column.
Reviewing Imported Object Links
A list of links between objects that were imported is included in the import log file. You can display only the imported links and their related objects by adding filters to the log file and filtering on the importLink value in the OPERATION2 column. The link identities and information about the related objects are displayed in the MESSAGE-VALUE column.
Reviewing Objects Imported with Conflicts
Information on each conflict that is encountered is included in the import log file. You can use the import log file to determine which conflicts were identified and which were addressed. To review conflicts generated during object import, add filters to the log file and filter on the Conflict value in the OPERATION2 column. Information about the object identity, the conflict type, and possible resolutions are displayed in various columns.
Reviewing Objects Ignored on Import
Some objects may not be supported for import into your Windchill system. Most often this is because the sending system is at a newer release of Windchill. If an unsupported object is included in your delivery, it is ignored on import. To review which objects were ignored for import, add filters to the log file and filter on the IGNORE value in the OPERATION2 column.
Was this helpful?