Opening a Partially Imported Family Table in Creo and SolidWorks
In the below table, Family Table FT1 A.1 exists on both the source and target systems. On the source system, FT1 A.1 includes two instances: Instance001 A.1 and Instance002 A.1. On the target system, FT1 A.1 includes only Instance001 A.1.
Meanwhile, Instance002 A.1 exists on the target system as a standalone CAD object, which matches the instance on the source system. Additionally, Instance002 A.2 is an iteration of this standalone object, creating a version mismatch between Instance002 A.2 on the target system and Instance002 A.1 on the source system.
On the target system, the following are marked for replication:
• FT1 A.1
• FT1.ASM A.1 (the assembly)
• Instance001 A.1
• Instance002 A.1 (standalone)
• Instance002 A.2 (iteration of the standalone)
|
Source System
|
Target System
|
|
FT1 A.1
|
FT1 A.1
|
|
Instance001 A.1
|
Instance001 A.1
|
|
Instance002 A.1
|
Instance002 A.1 (standalone)
|
|
Instance002 A.2 (iteration)
|
When you attempt to import the package, a non-overridable conflict occurs for Instance002 on the target system due to the version mismatch.
To resolve this, re-import the package and choose to skip both Instance002 A.1 and Instance002 A.2 on the target system. This allows the import to complete successfully, and FT1 A.1 along with Instance001 A.1 are overwritten.
After import:
• FT1 A.1 and Instance001 A.1 are now admin-locked
• Instance002 A.1 and Instance002 A.2 retain their Lock for Replication.
Behavior in CAD Tools
• In Creo: The tool successfully opens the admin-locked Family Table and removes parts (and their iterations) that match the Family Table instances on the source system, such as Instance002.
• In SolidWorks: The tool also opens the admin-locked Family Table, but instead of removing the parts, it creates ghost objects for parts and iterations that match source system instances again, like Instance002.