Conflict Messages for Import
This section describes the potential conflicts that can occur when importing information into the Windchill database. Information can be introduced or added into Windchill through many different ways, but conflicts are unique to the import functionality of Windchill. Examples of this functionality include Windchill packages, the Import/Export Management utility, and the Import from Spreadsheet action.
• For Windchill packages, the conflicts can appear in the Event Management utility and the Preview Received Delivery Import window.
• For the Import/Export Management utility, the conflicts appear in the Import Status Log section of the Import window.
• For the Import from Spreadsheet action, the conflicts appear in the Import Job Monitor and import job information page.
Conflicts occur when the import encounters an unexpected situation. Potential conflicts happen when Windchill objects being imported exist in the Windchill database, and the object properties of the imported and existing objects do not match.
In general, there are three types of conflicts:
• Administrative conflicts—Mismatches between data infrastructure (for example, the existence of folders, life cycles, or reusable attribute definitions) required by the imported object and the data definitions which exist in the target Windchill environment.
• Dependency conflicts—References in the imported object (for example, through part structure) to other business items that do not exist in the target system.
• Metadata conflicts—Mismatches between the metadata of items (for example, name/number pair) in the target system with the metadata of imported object occurs.
Many conflicts are presented in a generic message that the software supplies additional information to fit each situation:Object <type> already exists in database, but has different value for attribute <type>: existing value is <type>, new value is <type>.
A conflict is either overridable or non-overridable. Non-overridable conflicts are used for unexpected situations where the import cannot determine a resolution for the situation. An overridable conflict represents a situation where there are one or more possible resolutions and one of these resolutions is identified as the default resolution. Most uses of import support the options of automatically applying the default resolution to any overridable conflict encountered.
Through import on a received delivery, Windchill packages provide the ability to apply the default resolution to any overridable conflict encountered. They also allow the use of any specified resolution. Any conflict, where a resolution is not already specified, is presented in the Event Management Utility. For overridable conflicts, the user can select the resolution from the list of available resolutions. After a resolution has been selected for each conflict, the user can retry the import.
The following tables list the properties of Windchill objects that can cause conflicts for any use of import.
• Conflict Description: Message displayed in a window or the Event Management utility
• Explanation: Definitions of variables in the message
• Overridable: Yes if users can resolve the conflict or No if it fails automatically
• Default Resolution: The result that occurs if users select all default resolutions on import
• Available Resolutions: Options that appear if users opt not to accept default resolutions on import (These apply to packages only.)
|
|
Default IXB Resolution lets the import process continue and resolves the problem reported by the conflict. Users have the option to select this resolution from the event console.
|
