Part name is not unique for instances

[Ketan_Lalcheta]

Hi

I have created two CAD objects of Creo part type.... They are having name as P1.prt and P2.prt

Both of these parts have family table instances as instance1.

Now, I am connecting to windchill from Creo and tries to check in P1.prt which gets checked in successfully.

Post this, check in of P2.prt fails throwing an error that instance.prt model is not unique.

How to avoid this issue while check in into windchill...?

For us as cad, P1 and P2 are already unique files which are physical files... Instances details are inside generic part files P1 and P2. How to check in these two part files without changing any name of isntances?

Thanks and Regards
Ketan

[BenLoosli · Accepted solution]

You can't! Each file in Windchill MUST have a unique name.

You could create your instances as P1_instance1 and P2_instance 1 and be good.

As a side note, using such simple short names is also asking for troubles in a Windchill environment. Not from a system standpoint directly but from a unique naming convention.

[MikeLockwood]

For a family table in Windchill, look at the Content tab for the Generic and each Instance.  Only the Generic has a file. The database enforces uniqueness of the CAD Document Number; for family tables, multiple objects utilize and are mapped to the same filename.

[Ketan_Lalcheta]

Hi

Does this mean that all instances across CAD files must have unique name?

If so, we have landed into a difficult situations. We have almost 5k files having issues of unique name due to part file family instances. Even if we change name of isntances as unique for all part files , we would end up with missing references for assemblies which are having non unique instances as reference to them. So, there could be n number of complications with rename of instances as cad data dont enforce to have uniqye name for instances ...

Is there a way to handle this situation ?

[STEVEG]

All CAD objects in the system must be a unique File Name and Number.  In our system, and many others, the File Name and Number must be the same.  It doesn't matter if it's an assembly, part, generic, instance or drawing.

[BenLoosli]

If your designers have been building family tables with the default Instance_# for the instances, then you are in big trouble trying to load that data into Windchill.

Give us a better description of HOW you are using family tables and we may come up with something that may help.

If you need to rename your instances to load them into Windchill, I would load the assemblies first, then 1 generic part at a time. Let Windchill handle the rename and association of the new names in the assemblies. The caution here is that you will need to load ALL assemblies into Windchill that use the to-be renamed genric to capture all of the references.