|
Label in the report
|
Type of Conflict Message
|
Suggested Action
|
|
The following objects with the same file name already exist in target.
|
Object-level
|
• Ignore the complete package.
• Rename the object either in the source PLM system or the target PLM system, depending on which PLM system owns the object.
|
|
Cannot rename bolt.prt to bolt1.prt as object with the same name exists.
|
Object-level
|
• Ignore the complete package.
• Rename the object either in the source PLM system or the target PLM system, depending on which PLM system owns the object.
|
|
You do not have authorization to modify the following objects.
|
Definition-level
|
While exporting do not include these objects in the package. While importing do not import this package.
|
|
The following objects are expected to exist in the target PLM system, but they do not exist in the target PLM system.
|
Object-level
|
Expected files available in the target PLM system with same Object ID.
|
|
The lifecycle state/ release level of the following objects could not be updated.
|
Object-level
|
Manually change the life cycle state of this object in the target PLM system to see the reason for the conflict and its resolution.
|
|
File Name could not be updated for the following objects.
|
Object-level
|
Rename this object in the target PLM system to see the reason for the conflict and its resolution.
|
|
The following missing dependents could not be resolved.
|
Object-level
|
You must create these objects in the target PLM system.
|
|
The following objects were saved using later version of Creo.
|
Object-level
|
Use a later version of Creo Parametric to perform the import.
|
|
• The following folders could not be created.
• Mapping file provides an invalid folder name.
• You have no authorization to create a particular folder.
|
Definition-level
|
• Create the folder manually in the target PLM system to see the reason for the conflict and its resolution.
• Review the folder mapping.
|
|
The following target locations have incompatible release scheme/lifecycle.
|
Definition-level
|
• Change the mapping to map to a valid release level or life cycle state.
• Create a valid definition for the release scheme or release state in the target PLM system.
|
|
The following target locations have incompatible release level/lifecycle state mapping.
|
Definition-level
|
• Change the mapping to a valid one.
• Create a valid definition in the target PLM system.
|
|
The following revisions do not exist in the target PLM system.
|
Definition-level
|
• Create a corresponding revision in the target PLM system, if it is allowed in your PLM system.
• Map the missing revision to an existing revision in the target PLM system.
|
|
The following revisions have been mapped from multiple source revisions.
Multiple revisions from a single revision scheme in the source PLM system are mapped to a single revision in the target PLM system.
|
Definition-level
|
Map a single version from a revision scheme to only one revision in the target PLM system.
|