Windchill System Administrator's Guide

Domain
Folder
Context
the team package doesn't provide an API method to reassign
TeamTemplate for an object that is being checked out.
– Modify non-versioned attributes -- The team of the newly created object
is the team from the XML file.
– Update checked out object in place-- The team of the newly created object
is the team of the checked out object in the database. This behavior is
chosen because the team package doesn't provide an API method to
reassign TeamTemplate for an object that is being checked out.
There are 2 cases in which a domain conflict occurs:
• The domain of the object in the XML file doesn't exist in the database, in
which case import fails -- a non-overridable conflict.
• The domain of the object in the XML file is different from the one in
database, in which case the following import actions yield the following
results:
– Default -- The database object remains unchanged.
– All other actions -- The domain of the newly created object is the domain
of the existing object in the database.
There are 2 cases in which a folder conflict occurs:
• The domain of the object in the XML file doesn't exist in the database, in
which case import fails -- a non-overridable conflict.
• The domain of the object in the XML file is different from the one in
database, in which case the following import actions yield the following
results:
– Default -- The database object remains unchanged.
– All other actions -- The folder of the newly created object is the folder of
the existing object in the database.
If there is no context mapping file, the object will be imported to the context from
where the import process is launched.
If there is context mapping file, the object will be imported according to the
mapping file. If the mapping file maps the object to a context that doesn't exist,
the import process throws an exception.
Import and Export Policies, Mapping Rules, and Conflict Messages C-23