|
Before importing a received delivery, verify that the version information mapping is correctly defined. The message displayed in the Context Related Information section in the Preview Received Delivery Import dialog box indicates the version mapping configured in the target system. In case of implicit mapping, the message is “Displays potential issues for the current received delivery influenced by your intended import selections. Issues identified in this section can be addressed by changing your selections when completing the Import action, by updating your mapping definitions, or by creating the necessary information in Windchill.”
However, when the target system uses the version information from the source system without implicit mapping, the message is “Displays potential issues identified for the current delivery due to the selected context mapping or the retained version labels from the source system. You can address these issues by changing your selections during the import, updating your mapping definitions, or creating the necessary information in Windchill.”
|
Tab
|
Description
|
---|---|
Current Context
|
Uses the current context, instead of the context supplied by the source system, as the target context for all imported objects. No conflicts related to the mapped context are listed.
The current context is used to translate all other attributes that can be mapped. If there is no mapping specified for each of these attributes, Windchill searches for the same attribute on the current system. If a match is not found and no mapping is specified, a conflict is listed. For more information, see Defining Received Delivery Mapping.
This tab is selected by default if you are importing a PTC Windchill formatted package.
|
Mapped Context
|
Uses the context supplied by the source system. If there is no defined context mapping, Windchill searches for the same context on the current system. If there is no matching context, a conflict is listed.
If a context is identified, the selected context is used to translate all other attributes that can be mapped. If there is no mapping specified for each of these attributes, Windchill searches for the same attribute on the current system. If a match is not found and no mapping is specified, a conflict is listed. For more information, see Defining Received Delivery Mapping.
This tab is selected by default if you are importing a PTC Windchill formatted package that contains replication data.
|
Label | Description |
---|---|
Conflict Type | The reason for the conflict. For example, if you do not have the appropriate permissions for the mapped folder, the conflict appears as FOLDER_NOT_AUTHORIZED. |
Conflict Description | Additional details about the conflict. For example, if a folder is not available in the current or mapped context, the folder and context names are listed. |
Resolution | The available stored resolution, if any. |
Source Value | The attribute from the source system. For example, the context on the source system from which the object originated. |
Mapped Value | The mapped attribute on the target system. |
A log file containing the conflicts also appears in the Attachments table on the Attachments tab of the received delivery information page. |
If security labels are enabled on the source system, but not on the target system, security label mapping conflicts are displayed. However, security labels applied to objects in the delivery ZIP files are ignored when the received delivery is imported to the target system if security labels are not enabled. For more information, see Security Label Mapping. |