Windchill System Administrator's Guide

conflict is overridable or not is dependent on the target database, the jar file
(containing metadata XML files and content files) to be imported, as well as
the import actions. Selecting the checkbox Resolve Overridable Conflicts
will only resolve the overridable conflicts and can not resolve the nonoverridable
conflicts. If there are one or more non-overridable conflicts, the
import operation fails. If failure occurs, in order to have a successful import
operation, something must be done prior to the next attempt to do the same
import operation. For example, apply a mapping rule file to the XML files to
ensure no non-overridable conflicts will happen against the target database.
Note: A particular change for the 7.0 release that can produce conflicts
involves the RatioDefinition and RatioValue. These types of data, if included
in an export from 6.2.6 or earlier, result in an overridable import conflict in
the 7.0 release. If you override the conflict, the data is imported as
FloatDefinition and FloatValue.
7. You may click Preview to understand what will be imported. With Detailed
Log cleared, you can see how many objects will be imported and how many
XML files will be processed. With Detailed Log checked, you can see what
files will be imported, what conflicts may arise during import, and whether
the import process will be completed or will fail. PTC recommends using
Preview, especially for checking the effect of policy files, which have the
potential of creating significant changes to the database. The Preview
operation does not perform actual import, nor does it report all conflicts,
especially those from runtime.
8. Click Submit.
Messages in the Import Status Log section of the Import window show progress or
problems that you can resolve. See the appendix that explains policy files,
mapping rules, and conflict messages in the Windchill System Administrator's
Guide for information that can help in resolving conflicts.
Additional Export and Import Actions
Additional Lock Export Action
Additional Import Actions
The following export and import actions are available, but are not presented as
options in the graphical user interface.
The Lock action can be imposed through an import policy file or the system
registry.
These actions are imposed through an import policy file or the system registry:
• UnlockAndIterate -- This action finds an object in the database with the same
UFID or the same name, number, version, and iteration as the object in the
XML file. If such an object exists and it is locked, this action unlocks and
Windchill Import and Export 6-19