Enterprise Administration > Business Administrative Change Promotion > Running the Business Administrative Change Promotion Command-Line Utility > Business Administrative Change Promotion Conflicts > Import conflict
Import conflict
Conflict Resolution from Event Management
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.
For more information about conflicts and a list of general conflicts that can occur during import, see Conflict Messages for Import.
When importing to a selective system, the usual default resolution is to override any conflict that occurs for an object on the target system with the new or update object from the source system. When importing to a synchronized system, the default resolution is to retry the import. Retrying the import often requires a manual action by the importing user to resolve the conflict. After resolving the issue, the import can be retried using the Event Management utility.
Conflict Resolution using Event Management utility
The first table lists the conflict messages that are specific to importing administrative objects using the business administrative change promotion command-line utility.
• Conflict Description: Message displayed on the command prompt or in the Event Management utility.
• Explanation: Describes the problem that has occurred.
• Available Resolutions: Options that appear if users opt not to accept default resolutions on import.
Conflict Resolution using XML File
The second table lists the valid values for the type of conflict and possible resolutions that you can use in a conflict resolution XML file for import conflicts:
• Conflict Description: Message displayed on the Event Management utility.
• ConflictType Constant: Specifies the valid value for a ConflictType element in the XML file.
• Resolution Constant: Specifies the valid value for a Resolution element in the XML file.
Common Conflicts
Conflict Description
Explanation
Available Resolutions
User does not have read permission on context.
The user running the utility does not have the appropriate permissions to update an object in a particular context.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
User does not have create permission for the following object: <object identity>
The user running the utility does not have the appropriate permissions to create an imported object on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
The following attribute does not exist: <attribute identity>
An attribute on an imported object does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import
The following organization does not exist: <organization name>
An organization referenced by an object being imported does not exist on the target system.
• Manually create the missing organization and then retry the import.
• Skip the object import — only valid in selective mode.
• Use the existing organization — only valid in selective mode in systems with one organization.
The following context does not exist: <context name>
A context referenced by an object being imported does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
The type identifier <object type> cannot be found. See the Basic Administration for further information.
An object type referenced by an object does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
The user <user name> does not exist.
A user does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
The following context does not exist: <container path>.
A container does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
User does not have modify permission for the following object: <object name>
The user running the utility does not have the appropriate permissions to create, update, or delete an imported object on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
The object <name> could not be imported because the container <name> was not found.
The referenced application container or organization for an object being imported does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
Common Conflicts
Conflict Description
ConflictType Constant
Resolution Constant
User does not have read permission on context.
NO_READ_ACCESS_TO_CONTAINER
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
User does not have create permission for the following object: <object identity>
NO_CREATE_ACCESS_FOR_OBJECT
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
The following attribute does not exist: <attribute identity>
ATTRIBUTE_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The following organization does not exist: <organization name>
ORGANIZATION_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
• USE_DEFAULT_ORGANIZATION (selective and development)
The following context does not exist: <context name>
CONTAINER_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
User does not have modify permission for the following object: <object name>
NO_MODIFY_ACCESS_FOR_OBJECT
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
The type identifier <object type> cannot be found. See the Basic Administration for further information.
TYPE_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
The user <user name> does not exist.
USER_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
The following context does not exist: <container path>.
CONTAINER_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
The object <name> could not be imported because the container <name> was not found.
CONTAINER_DOES_NOT_EXIST_CONFLICT
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
Profile Conflicts
The following table provides information on conflicts that can occur during importing Profiles with available resolutions:
Conflict Description
Explanation
Available Resolutions
A profile <profile name> has a later modified date and time on the target system than the version being imported.
A profile on the target system was modified later than the same profile that is being imported from the source system.
• Overwrite the profile on the target system with the profile from the source system.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
A profile with the name <profile name> already exists in the following context: <context name>
A profile with the same name as a profile being imported already exists in the target system.
• Overwrite the profile on the target system with the profile from the source system.
• Manually resolve the issue and retry the import.
The conflict message is used when import fails because the participant <participant name> does not exist.
* 
Before importing ensure that the participant is already loaded in the target system.
The participant does not exist in the target system due to which the import fails.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in sync mode.
The following organization does not exist: <organization name>
* 
Before importing ensure that the organization <organization name> is already loaded in the target system.
When importing a profile in the target system if the organization <organization name> does not exist then the import fails.
• Manually create the missing organization and then retry the import.
• Skip the object import — only valid in selective mode.
• Use default organization — only valid in selective mode in systems with one organization.
The conflict message is used when import fails because attribute <attribute identity> does not exist.
* 
Before importing ensure that the attribute <attribute identity> is already loaded in the target system.
An attribute does not exist in the target system due to which the import fails.
• Skip the object import — only valid in selective mode.
• Manually resolve the issue and retry the import.
Conflict Description
ConflictType Constant
Resolution Constant
Profile <profile name> has a later modified date and time on the target system than the version being imported.
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• OVERWRITE
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
A profile with the name <profile name> already exists in the following context: <context name>
PROFILE_NAME_EXISTS_IN_SAME_CONTEXT
• OVERWRITE
• RETRY_IMPORT
The conflict message is used when import fails because the participant <participant name> does not exist.
MEMBERS_NOT_FOUND
• RETRY_IMPORT (default)
• SKIP_OBJECT_IMPORT (Sync mode only)
The conflict message is used when import fails because when importing a profile in the system, the organization <organization name> does not exist.
ORGANIZATION_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
• USE_DEFAULT_ORGANIZATION (selective and development)
The conflict message is used when import fails because attribute <attribute identity> does not exist.
ATTRIBUTE_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
Policy Access Control Rule Conflicts
The following table provides information on conflicts that can occur during importing Policy Access Control Rule with available resolutions:
Conflict Description
Explanation
Available Resolutions
The user does not have access to domain <domain name> or it does not exist.
A domain referenced by a policy access control rule does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
<Object identity> cannot be imported because you do not have authorization for participant <participant name> or the participant does not exist.
A user, group, organization, or role referenced by an object being imported does not exist on the target system or the participant running the utility does not have the appropriate permissions to view the participant.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
* 
By default, participants are matched based on distinguished name. The Business Administrative Change Promotion > Participant Identification Using Additional Attributes preference is available to match participants based on attributes such as name, context, or email, depending on the participant type.
An access control rule with the following identity already exists: Domain <domain name>, type <object type>, state <life cycle state>, principal <user, group, organization, or role name>, AllExceptPrincipal <true or false>
A policy access control rule with the same identifying information as a policy access control rule being imported already exists in the target system.
• Manually resolve the issue and retry the import.
• Overwrite the policy access control rule on the target system with the policy access control rule from the source system — only valid in synchronized mode.
• Skip the object import — only valid in selective mode.
Conflict Description
ConflictType Constant
Resolution Constant
The user does not have access to domain <domain name> or it does not exist.
DOMAIN_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
<Object identity> cannot be imported because you do not have authorization for participant <participant name> or the participant does not exist.
PRINCIPAL_REF_PARTICIPANT_NOT_FOUND
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
An access control rule with the following identity already exists: Domain <domain name>, type <object type>, state <life cycle state>, principal <user, group, organization, or role name>, AllExceptPrincipal <true or false>
ACCESS_CONTROL_RULE_ALREADY_EXISTS
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
• OVERWRITE (synchronized mode only)
Object Initialization Rule Conflicts
The following table provides information on conflicts that can occur during importing Object Initialization Rule with available resolutions:
Conflict Description
Explanation
Available Resolutions
OIR <object identity> has a later modified date and time on the target system than the object being imported.
An object initialization rule (OIR) on the target system was modified later than the same OIR that is being imported from the source system.
• Skip the object import.
• Overwrite the OIR on the target system with the OIR from the source system
The OIR <object name> could not be imported because the container <container path> was not found.
* 
Before importing ensure that the container <container path> is already loaded in the target system.
The referenced application container or organization for an OIR being imported does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
An OIR with same identity already exists in the following context: <Container path>
An OIR with the same name as an OIR being imported already exists in the target system.
• Overwrite the OIR on the target system with the OIR from the source system.
• Skip the object import — only valid in selective mode.
• Manually resolve the issue and retry the import.
An Enabled OIR object for Object type <Type of object> already exists in the following context: <Container path>
An OIR with Enabled status for the object type being imported already exists in the target system.
• Disable the OIR and retry the import.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
The conflict message is used when import fails because when importing an Object Initialization Rule in the system, the organization <organization name> does not exist.
* 
Before importing ensure that the organization <organization name> is already loaded in the target system.
When importing an Object Initialization Rule in the target system if the organization <organization name> does not exist then the import fails.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
• Use default organization — only valid in selective mode in systems with one organization.
The type identifier <object type> cannot be found.
* 
Before importing ensure that the type identifier <object type> is already loaded in the target system.
When importing an Object Initialization Rule in the target system if the <object type> cannot be found then the import fails.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
Conflict Description
ConflictType Constant
Resolution Constant
OIR <object identity> has a later modified date and time on the target system than the object being imported.
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• SKIP_OBJECT_IMPORT
• OVERWRITE
The OIR <object name> could not be imported because the container <container path> was not found.
CONTAINER_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
An OIR with same identity already exists in the following context: <Container path>
OIR_WITH_SAME_IDENTITY_EXISTS
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
• OVERWRITE
An Enabled OIR object for Object type <Type of object> already exists in the following context: <Container path>
ANOTHER_OIR_WITH_ENABLED_STATUS_EXISTS
• DISABLE_AND_IMPORT
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
The following organization does not exist: <organization name>
ORGANIZATION_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
• USE_DEFAULT_ORGANIZATION (selective and development)
The type identifier <object type> cannot be found.
TYPE_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
Preference Conflicts
The following table provides information on conflicts that can occur during importing Preference with available resolutions:
Conflict Description
Explanation
Available Resolutions
The parent preference client <client name> for preference client <client name> does not exist.
A parent preference client does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
The preference client <client name> has a later modified date and time on the target system than the object being imported.
A preference client on the target system has been updated.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import — only valid in selective mode.
A preference client with identity <client name> already exists in the system.
A preference client with the same name already exists on the target system.
• Manually resolve the issue and retry the import.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import — only valid in selective mode.
The parent preference category <category name> for category <category name> does not exist.
A parent preference category does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
The parent preference category <category name> has a later modified date and time on the target system than the object being imported.
A preference category on the target system has been updated.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import — only valid in selective mode.
A preference category with name <category name> already exists in the system.
A preference category with the same name already exists on the target system.
• Manually resolve the issue and retry the import.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import — only valid in selective mode.
The preference definition <definition name> has a later modified date and time on the target system than the object being imported.
A preference definition has been updated on the target system.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import — only valid in selective mode.
A preference definition with identity <definition name> already exists in the system.
A preference definition with the same name already exists on the target system.
• Manually resolve the issue and retry the import.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import — only valid in selective mode.
The preference instance is locked.
The updates of a preference instance cannot be imported because the preference instance is locked at the organization or site container level in the target system.
• Manually resolve the issue and retry the import.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import — only valid in selective mode.
The following preference definition does not exist in the system: <definition name>.
A preference definition does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
The preference client <client name> does not exist.
A preference client does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
A preference instance with definition <definition name> , client <client name> at \'{2}\' was modified on target system.
A preference instance on the target system has been updated.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import — only valid in selective mode.
A parent preference instance object for a multi valued preference with following identity does not exist in the system \'{0}\'.
A parent preference instance does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
A multi valued preference instance <value key> has a later modified date and time on the target system than the object being imported.
A multi valued preference instance on the target system has been updated.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import — only valid in selective mode.
A multi valued preference with following value key already exists in the system <value key>.
A multi valued preference instance with the same identity already exists in the target system.
• Manually resolve the issue and retry the import.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import — only valid in selective mode.
The following preference category does not exist in the system <category name>.
A preference category does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
The following preference definition does not exist in the system: <definition name>.
A preference definition does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective mode.
A preference category definition link for following definition has a later modified date and time on the target system than the object being imported: <definition name>.
A preference category definition link on the target system has been updated on the target system.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import — only valid in selective mode.
Conflict Description
ConflictType Constant
Resolution Constant
The parent preference client <client name> for preference client <client name> does not exist.
PARENT_OBJECT_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
The preference client <client name> has a later modified date and time on the target system than the object being imported.
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• OVERWRITE
• SKIP_OBJECT_IMPORT (selective and development)
A preference client with identity <client name> already exists in the system.
PREFERENCE_CLIENT_WITH_SAME_NAME_ALREADY_EXISTS
• RETRY_IMPORT
• OVERWRITE
• SKIP_OBJECT_IMPORT (selective and development)
The parent preference category <category name> for category <category name> does not exist.
PARENT_OBJECT_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
The preference category <category name> has a later modified date and time on the target system than the object being imported.
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• OVERWRITE
• SKIP_OBJECT_IMPORT (selective and development)
A preference category with name <category name> already exists in the system.
PREFERENCE_CATEGORY_WITH_SAME_NAME_ALREADY_EXISTS
• RETRY_IMPORT
• OVERWRITE
• SKIP_OBJECT_IMPORT (selective and development)
The preference definition <definition name> has a later modified date and time on the target system than the object being imported.
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• OVERWRITE
• SKIP_OBJECT_IMPORT (selective and development)
A preference definition with identity <definition name> already exists in the system.
PREFERENCE_DEFINITION_WITH_SAME_NAME_ALREADY_EXISTS
• RETRY_IMPORT
• OVERWRITE
• SKIP_OBJECT_IMPORT (selective and development)
The preference instance is locked.
PREFERENCE_INSTANCE_LOCKED
• RETRY_IMPORT
• OVERWRITE
• SKIP_OBJECT_IMPORT (selective and development)
The following preference definition does not exist in the system: <definition name>.
PREFERENCE_DEFINITION_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
The preference client <client name> does not exist.
PREFERENCE_CLIENT_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
A parent preference instance object for Multivalue preference with following identity does not exist in the system \'{0}\'.
PARENT_PREFERENCE_INSTANCE_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
A multi valued preference instance <value key> has a later modified date and time on the target system than the object being imported.
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• OVERWRITE
• SKIP_OBJECT_IMPORT (selective and development)
A multivalued preference with following value key already exists in the system <value key>.
MULTIVALUE_PREFERENCE_WITH_SAME_IDENTITY_ALREADY_EXISTS
• RETRY_IMPORT
• OVERWRITE
• SKIP_OBJECT_IMPORT (selective and development)
The following preference category does not exist in the system <category name>.
PREFERENCE_CATEGORY_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
The following preference definition does not exist in the system: <definition name>.
PREFERENCE_DEFINITION_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
A preference category definition link for following definition has a later modified date and time on the target system than the object being imported: <definition name>.
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• OVERWRITE
• SKIP_OBJECT_IMPORT (selective and development)
Lifecycle and Workflow Process Template Conflicts
The following table provides information on conflicts that can occur during importing Lifecycle and Workflow Process Template with available resolutions:
Conflict Description
Explanation
Available Resolutions
The task name <task type> does not exist for <activity name>.
A task name does not exist for the referenced activity.
• Manually resolve the issue and retry the import.
• Skip the object import.
The Workflow Process Template with following identity already exists: name <template name>, context <container name>.
A workflow process template with the same identifying information as a workflow process template being imported already exists in the target system.
• Iterate the object and retry the import.
• Manually resolve the issue and retry the import.
• Skip the object import.
The scope for the following Workflow Process Template cannot be narrowed: <template name>.
Change in the scope or hierarchy of a workflow process template is not supported.
• Manually resolve the issue and retry the import.
• Skip the object import.
A newer iteration of the following Workflow Process Template exists: name <template name>, context <container name>.
A newer iteration of the workflow process template that is being imported from the source system exists in the target system.
• Iterate the object and retry the import.
• Manually resolve the issue and retry the import.
• Skip the object import.
The Team Template <template name> does not exist within the container <container name>.
A Team Template does not exist in the specified container on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
The actor role <role name> does not exist for <node name>.
An actor role for the specified node does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
The role <role name> does not exist for <node name>.
A role for the specified node does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
The transition <transition name> does not exist for <node name>.
A transition for the specified node does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
The class type <Java class name used in customization> does not exist for <node name>.
The specified Java class does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
The following folder location for workflow template does not exist or user does not have access to it: <folder name>.
The folder specified for a workflow template does not exist on the target system or the user does not have access to the specified folder.
• Manually resolve the issue and retry the import.
• Skip the object import.
The following transition name does not exist: <transition name>.
The specified transition does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
The scope for the following Lifecycle Template cannot be narrowed: <lifecycle template name>.
Changing the scope or hierarchy of a lifecycle template is not supported.
• Skip the object import.
The following Lifecycle state does not exist: <name of state>.
A lifecycle state does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
The following series selector for Lifecycle Template does not exist: <series name>.
The referenced series collector does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
The following actor role for Lifecycle Template does not exist: <actor name>.
An actor role does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
The following supported class type does not exist: <supported class type>.
The specified Java class does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
The following role for life cycle template does not exist: <role name>
The specified role does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
The following Lifecycle Template is checked out: name <template name>, context <container>.
A lifecycle template is checked out on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
A newer iteration of the following Lifecycle Template exists: name <template name>, context <container>.
A newer iteration of the lifecycle template that is being imported from the source system exists in the target system.
• Iterate the object and retry the import.
• Manually resolve the issue and retry the import.
• Skip the object import.
A Lifecycle Template with following identity already exists: name <template name>, context <container>.
A lifecycle template with the same identifying information as a lifecycle template being imported already exists in the target system.
• Iterate the object and retry the import.
• Manually resolve the issue and retry the import.
• Skip the object import.
The required dependent Workflow Template not found: <Workflow Template name>
A dependent workflow template does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
The following folder location for life cycle template does not exist or user does not have access to it: <folder name>.
The folder specified for a lifecycle template does not exist on the target system or the user does not have access to the specified folder.
• Manually resolve the issue and retry the import.
• Skip the object import.
Conflict Description
ConflictType Constant
Resolution Constant
The state <name> does not exist for <type name>.
STATE_DOES_NOT_EXISTS
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The task name <task type> does not exist for <activity name>.
TASK_NAME_DOES_NOT_EXISTS
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The Workflow Process Template with following identity already exists: name <template name>, context <container name>.
WORKFLOW_WITH_SAME_IDENTITY_EXISTS
• ITERATE
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The scope for the following Workflow Process Template cannot be narrowed: <template name>.
WORKFLOW_CANNOT_NARROW_SCOPE
• SKIP_OBJECT_IMPORT
The following Workflow Template is checked out: name <template name>, context <container name>.
WORKFLOW_CHECKED_OUT
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
A newer iteration of the following Workflow Process Template exists: name <template name>, context <container name>.
WORKFLOW_NEWER_ITERATION_EXIST
• ITERATE
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The Team Template <template name> does not exist within the container <container name>.
TEAM_TEMPLATE_DOES_NOT_EXISTS
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The actor role <role name> does not exist for <node name>.
ACTOR_ROLE_DOES_NOT_EXISTS
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The role <role name> does not exist for <node name>.
ROLE_DOES_NOT_EXISTS
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The transition <transition name> does not exist for <node name>.
TRANSITION_DOES_NOT_EXISTS
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The class type <Java class name used in customization> does not exist for <node name>.
VARIABLE_CLASS_DOES_NOT_EXISTS
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The following folder location for Workflow Template does not exist or user does not have access to it: <folder name>.
WORKFLOW_FOLDER_LOCATION_NOT_FOUND
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The following transition name does not exist: <transition name>.
LCT_TRANSITION_NAME_NOT_FOUND
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The scope for the following Lifecycle Template cannot be narrowed: <lifecycle template name>.
LCT_CANNOT_NARROW_SCOPE
• SKIP_OBJECT_IMPORT
The following Lifecycle state does not exist: <name of state>.
LCT_STATE_NOT_FOUND
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The following series selector for Lifecycle Template does not exist: <series name>.
LCT_SERIES_SELECTOR_NOT_FOUND
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The following actor role for Lifecycle Template does not exist: <actor name>.
LCT_ACTOR_ROLE_NOT_FOUND
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The following supported class type does not exist: <supported class type>.
LCT_SUPPORTED_CLASS_NOT_FOUND
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The following role for Lifecycle Template does not exist: <role name>.
LCT_ROLE_NOT_FOUND
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The following Lifecycle Template is checked out: name <template name>, context <container>.
LCT_CHECKED_OUT
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
A newer iteration of the following Lifecycle Template exists: name <template name>, context <container>.
LCT_NEWER_ITERATION_EXIST
• ITERATE
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
A Lifecycle Template with following identity already exists: name <template name>, context <container>.
LCT_WITH_SAME_IDENTITY_EXISTS
• ITERATE
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The required dependent Workflow Template not found: <Workflow Template name>.
WORKFLOW_NOT_FOUND
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
The following folder location for Lifecycle Template does not exist or user does not have access to it: <folder name>.
LCT_FOLDER_LOCATION_NOT_FOUND
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
Type Definition Conflicts
The following table provides information on conflicts that can occur during importing Type Definition with available resolutions:
Conflict Description
Explanation
Available Resolutions
The following type definition has a later modified date and time on target system than the object imported: <Object name>
One or more types has been modified in the target system.
LWCType definition which was exchanged previously through the BAC package has been modified in the target system.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import.
Parent type definition <Name of the ancestor> for type definition <object name> does not exist.
One or more ancestors of the type does not exist on the target system.
* 
This conflict will not be thrown if the ancestor element is present in the zip file.
Skip the object import.
The ancestor type <Name of the ancestor>of the following type definition has a later modified date and time on the target system than the object being imported: <Object name>
One or more ancestors of the type in the import set has been modified in the target system.
Skip the object import.
A type definition with following identity already exists: <Object name>: display name: Display name of the type definition, internal name: <Internal name of the type definition>, namespace: <Namespace of the type definition>flavor: <Attribute template flavour of the type definition>
One or more types with the same business identity was found on the target system but they have different remote IDs.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import.
• Manually resolve the issue and retry the import.
The following type definition is renamed on target system: <Object name>
One or more types in the import set cannot be found by business identity, but can be found by remote/local ids.
• Skip the object import.
• Rename the object on target system.
• Manually resolve the issue and retry the import.
The following type definition is renamed on source system: <Object name>
One or more types in the import set cannot be found by business identity, but can be found by remote/local ids
• Skip the object import.
• Rename the object on target system.
• Manually resolve the issue and retry the import.
Conflict Description
ConflictType Constant
Resolution Constant
The following type definition has a later modified date and time on target system than the object imported: <Object name>
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• OVERWRITE
• SKIP_OBJECT_IMPORT
Parent type definition <Name of the ancestor> for type definition <object name> does not exist.
PARENT_TYPE_DOES_NOT_EXIST
SKIP_OBJECT_IMPORT
The ancestor type <Name of the ancestor>of the following type definition has a later modified date and time on the target system than the object being imported: <Object name>
TYPE_ANCESTOR_ON_TARGET_HAS_BEEN_UPDATED
SKIP_OBJECT_IMPORT.
A type definition with following identity already exists: <Object name>: [display name: Display name of the type definition, internal name: Internal name of the type definition, namespace: Namespace of the type definition, flavor: Attribute template flavour of the type definition].
TYPE_WITH_SAME_IDENTITY_EXISTS
• OVERWRITE
• SKIP_OBJECT_IMPORT
• RETRY_IMPORT
The following type definition is renamed on target system: <Object name>
TYPE_RENAMED_ON_TARGET
• SKIP_OBJECT_IMPORT
• OVERWRITE
• RETRY_IMPORT
The following type definition is renamed on source system: <Object name>
TYPE_RENAMED_ON_SOURCE
• SKIP_OBJECT_IMPORT
• OVERWRITE
• RETRY_IMPORT
Quantities of Measure Conflicts
The following table provides information on conflicts that can occur during importing quantities of measure with available resolutions:
Conflict Description
Explanation
Available Resolutions
User does not have create permission for the following object: <Object name>
The user running the utility does not have the appropriate permissions to create an imported object on the target system
• Manually resolve the issue and retry the import.
• Skip the object import – valid only in selective and development modes.
User does not have modify permission for the following object: <object name>
The user running the utility does not have the appropriate permissions to update an imported object on the target system
• Manually resolve the issue and retry the import.
• Skip the object import – valid only in selective and development modes.
A Quantity of Measure with same identity already exists: < Object identity >
A quantity of measure with the same identity already exists in the target system.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import – valid only in selective and development modes.
<Object Name> has later modified date and time on the target system than the object being imported.
Quantity of measure on the target system has been updated.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import – valid only in selective and development modes.
• Retry- Manually resolve the issue and retry the import
Conflict Description
ConflictType Constant
Resolution Constant
User does not have create permission for the following object:<object identity>
NO_CREATE_ACCESS_FOR_OBJECT
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
User does not have modify permission for the following object: <object identity>
NO_MODIFY_ACCESS_FOR_OBJECT
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
A Quantity of Measure with same identity already exists: <object identity>
QOM_WITH_SAME_IDENTITY_EXISTS
• RETRY_IMPORT
• OVERWRITE
• SKIP_OBJECT_IMPORT
<object identity> has later modified date and time on the target system than the object being imported.
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• RETRY_IMPORT
• OVERWRITE
• SKIP_OBJECT_IMPORT
Measurement Systems Conflicts
The following table provides information on conflicts that can occur during importing measurement systems with available resolutions:
Conflict Description
Explanation
Available Resolutions
User does not have create permission for the following object: <object identity>
The user running the utility does not have the appropriate permissions to create an imported object on the target system
• Manually resolve the issue and retry the import.
• Skip the object import – valid only in selective and development modes.
User does not have modify permission for the following object:<object identity>
The user running the utility does not have the appropriate permissions to update an imported object on the target system
• Manually resolve the issue and retry the import.
• Skip the object import – valid only in selective and development modes.
A Measurement system with same identity already exists:<Object name>
A measurement system with the same identity already exists in the target system.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import – valid only in selective and development modes.
• Retry- Manually resolve the issue and retry the import
<Object name> has later modified date and time on the target system than the object being imported.
Measurement systems on the target system has been updated.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import – valid only in selective and development modes.
• Retry- Manually resolve the issue and retry the import
Conflict Description
ConflictType Constant
Resolution Constant
User does not have create permission for the following object: <Object name>
NO_CREATE_ACCESS_FOR_OBJECT
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
User does not have modify permission for the following object: <object name>
NO_MODIFY_ACCESS_FOR_OBJECT
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
A Measurement system with same identity already exists:<Object identity>
MS_WITH_SAME_IDENTITY_EXISTS
• RETRY_IMPORT
• OVERWRITE
• SKIP_OBJECT_IMPORT
<Object name> has later modified date and time on the target system than the object being imported.
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• RETRY_IMPORT
• OVERWRITE
• SKIP_OBJECT_IMPORT
Global Enumerations Conflicts
The following table provides information on conflicts that can occur when importing global enumeration, modeled enumeration, or custom UI text with available resolutions:
Conflict Description
Explanation
Available Resolutions
User does not have create permission for the following object: <Object identity>
The user running the utility does not have the appropriate permissions to create global enumeration, modeled enumeration, or custom UI text on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import – valid only in selective and development modes.
User does not have modify permission for the following object: <Object identity>
The user running the utility does not have the appropriate permissions to update an imported object on the target system
• Manually resolve the issue and retry the import.
• Skip the object import – valid only in selective and development modes.
A Global Enumeration with same identity already exists: <Object identity>
Global enumeration, modeled enumeration, or custom UI text with the same identity already exists in the target system.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import – valid only in selective and development modes.
Global Enumeration <Object identity> has a different master enumeration on the target system.
Global enumeration, modeled enumeration, or custom UI text has a different master enumeration on the target system.
• Skip the object import – valid only in selective and development modes.
* 
For the additional information about the skip resolution for this conflict, see the section after the following table.
• Retry- Manually resolve the issue and retry the import.
<Object identity> has later modified date and time on the target system than the object being imported.
Global enumeration, modeled enumeration, or custom UI text on the target system has been updated.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import – valid only in selective and development modes.
• Retry- Manually resolve the issue and retry the import.
An Organizer with same identity already exists:<organizer name>
An organizer with the same identity already exists in the target system.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import – valid only in selective and development modes.
• Retry- Manually resolve the issue and retry the import.
An Organizer <organizer name>has a later modified date and time on the target system than the object being imported
One or more enumeration organizer or text organizer on the target system has been updated.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import – valid only in selective and development modes.
• Retry- Manually resolve the issue and retry the import.
A Global Enumeration with same identity already exists <Object identity> under different Hierarchy
A global enumeration, modeled enumeration, or custom UI text with same identity already exists under different hierarchy
Retry and skip the object import.
An Organizer with same identity already exists: <organizer name> under different Hierarchy
An organizer with same identity already exists on target but under different hierarchy
Retry and skip the object import.
Conflict Description
ConflictType Constant
Resolution Constant
User does not have create permission for the following object: <Object identity>
NO_CREATE_ACCESS_FOR_OBJECT
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
User does not have modify permission for the following object: <object name>
NO_MODIFY_ACCESS_FOR_OBJECT
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
A Global Enumeration with same identity already exists: <object name>
ENUM_DEF_WITH_SAME_IDENTITY_EXISTS
• RETRY_IMPORT
• OVERWRITE
• SKIP_OBJECT_IMPORT
Global Enumeration <object name> has a different master enumeration on the target system.
ENUM_DEF_ON_TARGET_HAS_MASTER_MISMATCH
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
* 
For the additional information about the skip resolution for this conflict, see the section after this table.
An Organizer with same identity already exists: <organizer name>
ORGANIZER_WITH_SAME_IDENTITY_EXISTS
• RETRY_IMPORT
• OVERWRITE
• SKIP_OBJECT_IMPORT
An Organizer <organizer name> has a later modified date and time on the target system than the object being imported
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• RETRY_IMPORT
• OVERWRITE
• SKIP_OBJECT_IMPORT
<Object identity> has later modified date and time on the target system than the object being imported.
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• RETRY_IMPORT
• OVERWRITE
• SKIP_OBJECT_IMPORT
When skip resolution is applied on a global enumeration, modeled enumeration, or custom UI text that has a different master enumeration on the target system and the following is true, a complete hierarchy under the immediate organizer is skipped.
• The source and target systems are identical.
• The enumerations or custom UI text of the target and source systems have the same immediate parent organizer.
For example, enumeration definitions are same in the source and target systems as indicated in the following table:
Source
Target
Organizer1
Organizer1
• Organizer2
◦ Enumeration2A
◦ Enumeration2B
• Organizer3
◦ Enumeration3A
• Organizer2
◦ Enumeration2A
◦ Enumeration2B
• Organizer3
◦ Enumeration3A
For source and target systems, there is a parent organizer Organizer1, immediate organizers Organizer2 and Organizer3. The immediate organizer Organizer2 has enumerations Enumeration2A, and Enumeration2B.
The immediate organizer Organizer3 has enumeration Enumeration3A.
You update the Enumeration2A, Enumeration2B, and Enumeration3A in the target system by exporting a package from the source system and importing it to the target system. For such scenario, a conflict occurs and the message “A Global Enumeration with same identity already exists: <Object identity> is returned.
When you select the SKIP_OBJECT_IMPORT resolution for Enumeration2A and the OVERWRITE resolution for Enumeration2B and Enumeration3A, then the resolution process skips Enumeration2A. However, it also skips Enumeration2B though you have selected the OVERWRITE resolution for Enumeration2B because Enumeration2A and Enumeration2B have same the common immediate parent organizer, that is, Organizer2.
The target system imports Enumeration3A successfully because the immediate parent organizer is Organizer3.
Reusable Attributes Conflicts
The following table provides information on conflicts that can occur during importing reusable attributes with available resolutions:
Conflict Description
Explanation
Available Resolutions
User does not have create permission for the following object: <Object identity>
The user running the utility does not have the appropriate permissions to create attribute definition on the target system
• Manually resolve the issue and retry the import.
• Skip the object import – valid only in selective and development modes.
User does not have modify permission for the following object: <object identity>
The user running the utility does not have the appropriate permissions to update an imported object on the target system
• Manually resolve the issue and retry the import.
• Skip the object import – valid only in selective and development modes.
An Attribute definition with same identity already exists: <Object name>
An Attribute definition with the same identity already exists in the target system.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import – valid only in selective and development modes.
An Organizer with same identity already exists: <Organizer name>
An organizer with the same identity already exists in the target system.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import – valid only in selective and development modes.
• Retry- Manually resolve the issue and retry the import
An Organizer <organizer name> has a later modified date and time on the target system than the object being imported
Resuable attribute organizer on the target system has been updated.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import – valid only in selective and development modes.
• Retry- Manually resolve the issue and retry the import
<Object name> has later modified date and time on the target system than the object being imported.
Attribute definition on the target system has been updated.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import – valid only in selective and development modes.
• Retry- Manually resolve the issue and retry the import
Conflict Description
ConflictType Constant
Resolution Constant
User does not have create permission for the following object: <Object identity>
NO_CREATE_ACCESS_FOR_OBJECT
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
User does not have modify permission for the following object: <object name>
NO_MODIFY_ACCESS_FOR_OBJECT
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
An Attribute definition with same identity already exists: <object identity>
ATTRDEFN_WITH_SAME_IDENTITY_EXISTS
• RETRY_IMPORT
• OVERWRITE
• SKIP_OBJECT_IMPORT
<object identity> has later modified date and time on the target system than the object being imported.
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• RETRY_IMPORT
• OVERWRITE
• SKIP_OBJECT_IMPORT
An Organizer with same identity already exists: <organizer name>
ORGANIZER_WITH_SAME_IDENTITY_EXISTS
• RETRY_IMPORT
• OVERWRITE
• SKIP_OBJECT_IMPORT
An Organizer <organizer name> has a later modified date and time on the target system than the object being imported
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• RETRY_IMPORT
• OVERWRITE
• SKIP_OBJECT_IMPORT
The following is a sample conflict resolution XML file for import conflicts:
<BACConflictResolutionPairs>
<BACConflictResolutionPair>
<ConflictType>NO_READ_ACCESS_TO_CONTAINER</ConflictType>
<Resolution>SKIP_OBJECT_IMPORT</Resolution>
</BACConflictResolutionPair>
<BACConflictResolutionPair>
<ConflictType>PROFILE_NAME_EXISTS_IN_SAME_CONTEXT</ConflictType>
<Resolution>RETRY_IMPORT</Resolution>
</BACConflictResolutionPair>
<BACConflictResolutionPair>
<ConflictType>OBJECT_ON_TARGET_HAS_BEEN_UPDATED</ConflictType>
<Resolution>OVERWRITE</Resolution>
</BACConflictResolutionPair>
</BACConflictResolutionPairs>
Shared Table Views Conflicts
Conflict Description
Explanation
Available Resolutions
A Table View with the same identity already exists: <identity of the table>
A shared table view for a given UI already exists on the target system with the same name, creator, and context.
• Overwrite — the table view on the target system will be overwritten by the one from the source system.
• Skip the object import — only valid in selective modes. Retry import excluding this object.
A Table View with same identity already exists in another container : <identity of the table>
A Table View for a given UI already exists with same identity in another context.
• Skip the object import — only valid in selective modes. Retry import excluding this object.
• Retry import — Manually resolve the issue and retry the import.
The following context does not exist: <identity of the context>
The specific context or container does not exist.
Skip the object import — only valid in selective modes.
Table View already exists for another user.
Table view for the given UI exists with the same name and context that was deleted on the source.
• Force delete — deletes the existing table view.
• Retry import — Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective modes. Retry import excluding this object .
A Table View cannot be imported because the current user does not have the necessary permissions. <identity of the table>
Table View cannot be imported because the user does not have the necessary permission.
• Skip the object import — only valid in selective modes. Retry import excluding this object.
• Retry import — Manually resolve the issue and retry the import.
Conflict Description
ConflictType Constant
Resolution Constant
A Table View with the same identity already exists: <identity of the table>
BAC_TABLE_VIEW_EXISTS
• SKIP_OBJECT_IMPORT
• OVERWRITE (Default CCD value)
A Table View with same identity already exists in another container : <identity of the table>
BAC_TABLE_VIEW_EXISTS_IN_ANOTHER_CONTAINER
• SKIP_OBJECT_IMPORT
• RETRY_IMPORT (Default CCD value)
The following context does not exist: <identity of the context>
CONTAINER_DOES_NOT_EXIST
• SKIP_OBJECT_IMPORT
• RETRY_IMPORT
Table View already exists for another user
BAC_TABLE_VIEW_EXISTS_DELETE
• FORCE_DELETE (Default CCD value)
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
A Table View cannot be imported because the current user does not have the necessary permissions. <identity of the table>
BAC_TABLE_VIEW_USER_NOT_AUTHORIZED
• SKIP_OBJECT_IMPORT
• RETRY_IMPORT (Default CCD value)
Document Template Conflicts
The following table provides information on conflicts that can occur during importing document template with available resolutions:
Conflict Description
ConflictType Constant
Resolution Constant
A Document Template with same identity already exists
BAC_DOCTEMPLATE_WITH_SAME_IDENTITY_EXISTS
• OVERWRITE
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
Object has a later modified date and time on the target system than the version being imported.
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
<Generic conflict – add info already available for other Objects>
<Generic conflict – add info already available for other Objects>
NO_CREATE_ACCESS_FOR_OBJECT
<Generic conflict – add info already available for other Objects>
<Generic conflict – add info already available for other Objects>
NO_MODIFY_ACCESS_FOR_OBJECT
<Generic conflict – add info already available for other Objects>
A Document Template with same number <number> already exists: <object identity>
BAC_DOCTEMPLATE_WITH_SAME_NUMBER_EXISTS
• SKIP
• RETRY
* 
Most of the Document conflicts are applicable for Document template and additional resolutions for BAC such as RETRY_IMPORT and SKIP_OBJECT_IMPORT as applicable will be available for BAC import for all these conflicts.
Report Template Conflicts
The following table provides information on conflicts that can occur when importing report template with available resolutions:
Conflict Description
ConflictType Constant
Resolution Constant
A Report Template with same identity already exists
BAC_REPTEMPLATE_WITH_SAME_IDENTITY_EXISTS
• OVERWRITE
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
Object has a later modified date and time on the target system than the version being imported.
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• OVERWRITE
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
User does not have create permission for the following object: <object identity>
NO_CREATE_ACCESS_FOR_OBJECT
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
User does not have modify permission for the following object: <object name>
NO_MODIFY_ACCESS_FOR_OBJECT
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
Context Template Conflicts
The following table provides information on conflicts that can occur when a importing report with available resolutions:
Conflict Description
Explanation
Available Resolutions
A template with following identity already exists: name <template name>, context <container>
A template with the same identifying information as a context template being imported already exists in the target system.
• Iterate the object.
• Manually resolve the issue and retry the import.
• Skip the object import.
A context template <context template name> has a later modified date and time on the target system than the version being imported.
A context template on the target system has been updated.
• Overwrite the object on the target system with the object from the source system.
• Manually resolve the issue and retry the import.
• Skip the object import.
"ContextTemplate" cannot be imported because you do not have authorization for participant <participant name> or the participant does not exist.
The participant referenced by an object being imported does not exist on the target system or the participant running the utility does not have the appropriate permissions to view the participant.
• Set the current user.
• Manually resolve the issue and retry the import.
• Skip the object import — only valid in selective and development mode.
Conflict Description
ConflictType Constant
Resolution Constant
A template with following identity already exists: name <template name>, context <container>
CT_WITH_SAME_IDENTITY_EXISTS
• ITERATE
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
A context template <context template name> has a later modified date and time on the target system than the version being imported.
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• OVERWRITE
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
"ContextTemplate" cannot be imported because you do not have authorization for participant <participant name> or the participant does not exist.
PRINCIPAL_REF_PARTICIPANT_NOT_FOUND_RESOLUTIONSET_3
• Set Current User
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT (selective and development)
Report Conflicts
The following table provides information on conflicts that can occur when a importing report with available resolutions:
Conflict Description
Explanation
Available Resolutions
A report with same identity already exists: <report name>
A report with the same name already exists on the target system.
• Manually resolve the issue and retry the import.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import.
A report <report name> has a later modified date and time on the target system than the version being imported.
A report on the target system has been updated.
• Manually resolve the issue and retry the import.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import.
The following context does not exist in the system: <container path>
A container does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
User does not have create permission for the following object: <Object identity>
The user does not have the appropriate permissions to create a report on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
User does not have modify permission for the following object: <Object identity>
The user does not have the appropriate permissions to update an existing report on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
Conflict Description
ConflictType Constant
Resolution Constant
A report with same identity already exists: <report name>
BAC_REPORT_WITH_SAME_IDENTITY_EXISTS
• OVERWRITE (Default value)
• SKIP
• RETRY
A report <report name> has a later modified date and time on the target system than the version being imported.
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• OVERWRITE (Default value)
• SKIP
• RETRY
The following context does not exist in the system: <container path>
CONTAINER_DOES_NOT_EXIST
• SKIP
• RETRY (Default value)
User does not have create permission for the following object: <Object identity>
NO_CREATE_ACCESS_FOR_OBJECT
• SKIP
• RETRY (Default value)
User does not have modify permission for the following object: <Object identity>
NO_MODIFY_ACCESS_FOR_OBJECT
• SKIP
• RETRY (Default value)
Failure Scenarios
The import will fail if the corresponding customization artifacts are not available during the import. This includes input JSP file, resource bundle file (for all reports), folder path, folder name, and Jasper files for Jasper reports.
Scenario 1
Conflict code: BAC_REPORT_WITH_SAME_IDENTITY_EXISTS
When exporting a report from BAC, if a user selects a report that has a dependent report template with the same name, and if the Expose as Report value of the report template is set to true, then the user receives a "report already exists" conflict while importing on the source system. The user can use OVERWRITE as the default conflict resolver.
Scenario 2
Conflict code: OBJECT_ON_TARGET_HAS_BEEN_UPDATED
Based on scenario 1, if a report and report template have been imported into Windchill and the user tries to import an updated report, the user receives an "object has already been modified on target" conflict. Because in scenario 1, we are overwriting the report and the last updated time stamp will also get updated in the database. For this scenario, the user can use OVERWRITE as the default conflict resolver.
List-Based Versioning Scheme Conflicts
The following table provides information on conflicts that can occur when importing list-based versioning scheme with available resolutions:
Conflict Description
Explanation
Available Resolutions
List-based versioning scheme cannot be imported because the user does not have the necessary permission.
The list-based versioning scheme can only be imported by site administrators who are members of the Business Administrative Change Package Importer user group.
Skip the object import.
Errors found in the List-Based Versioning Scheme XML: <Error List>
The list-based versioning scheme XML is not valid.
Skip the object import.
Client Tab Conflicts
The following table provides information on conflicts that can occur when importing client tabs with available resolutions:
Conflict Description
Explanation
Available Resolutions
Type definition cannot be found in target or parent context: <object type>
An object type referenced by client tab does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
The user <user name> does not exist in the system.
Organization administrator user does not exist on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
The following context does not exist in the system: <context name>
An organization container for the client tab is not available on the target system.
• Manually resolve the issue and retry the import.
• Skip the object import.
Client tab with same identity already exists: <Object name>
The message appears when a client tab with the same identity already exists on the target system.
If the client tab was imported earlier on target and is renamed or deleted from source, it is renamed or deleted from the target system as well.
If the client tab was created earlier on target and is renamed or deleted from source, it is kept as is in the target system. There is no conflict reported.
• Manually resolve the issue and retry the import.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import.
Conflict Description
ConflictType Constant
Resolution Constant
Type definition cannot be found in target or parent context: <object type>
TYPE_DOES_NOT_EXIST
• SKIP
• RETRY
The user <user name> does not exist in the system.
USER_DOES_NOT_EXIST
• SKIP
• RETRY
The following context does not exist in the system: <context name>
CONTAINER_DOES_NOT_EXIST
• SKIP
• RETRY
Client tab with same identity already exists: <Object name>
CLIENT_TAB_WITH_SAME_IDENTITY_ALREADY_EXISTS
• OVERWRITE (Default value)
• SKIP
• RETRY
Rule Sets Conflicts
The following table provides information on conflicts that can occur when importing rule sets with available resolutions:
Conflict Description
Explanation
Available Resolutions
A rule set with the same identity already exists: <rule set name>
A rule set with the same name already exists on the target system.
• Manually resolve the issue and retry the import.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import.
A rule set <rule set name> has a later modified date and time on the target system than the version being imported.
A rule set on the target system has been updated.
• Manually resolve the issue and retry the import.
• Overwrite the object on the target system with the object from the source system.
• Skip the object import.
The following table provides information on the conflict description, ConflictType constant, and resolution constant:
Conflict Description
ConflictType Constant
Resolution Constant
Business Rule object <Object key> has a later modified date and time on the target system than the object being imported.
OBJECT_ON_TARGET_HAS_BEEN_UPDATED
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
• OVERWRITE
A Business Rule object with the same identity already exists: <Object identity>
BAC_BUSINESS_RULE_WITH_SAME_IDENTITY_ALREADY_EXISTS
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
• OVERWRITE
A Business Rule object does not exist in the BAC package: <Object key>
BAC_BUSINESS_RULE_OBJECT_DOES_NOT_EXIST
• RETRY_IMPORT
• SKIP_OBJECT_IMPORT
Was this helpful?