Cloning assembly doesn't renumber drawing (specification) Teamcenter

[jeffyounie]

I go through the whole "clone assembly" procedure and the drawing dataset keeps it's original number.

Teamcenter 8, NX6.

The teamcenter number of the item I'm cloning might start off as "1234" and the new number might be "5678" but when I look at the datasets in teamcenter, the item, item rev and model dataset have the new number ("5678") but the specification has the old teamcenter number ("1234"). If I open the new specification, it points to the new model and looks fine. What is happening?

NX 6.0.5.3 TC 8
Windows 7 64bit
Intel Xeon @3.07GHz - 8GB RAM
Nvidia Quadro 2000

 

[NXLars]

What does your output file say?

 

[looslib]

Is there a setting for clone the drawing with the model?
Did you specify the drawing file in your clone selection?


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[adam1986]

i have also noticed this when using cloned assemblies and auto-part tables.
The new cloned assembly part table still calls up the part it was cloned from, rather than the new parts.
I was told that you could open each part which has been affected by the clone and then use the following to reload the database attributes then use;

Format > Database Attributes > Reload.

but it didnt work, so still looking for a solution

Regards

Adam

 

[NXLars]

adam1986:
See my answer in this thread:

http://eng-tips.com/viewthread.cfm?qid=335410

Cloning are quite a confusing function if you don't handle it with some loving and caring.
The general behaviour is that if you clone an assembly, that assembly component/"file" should be listed at the top in the .clone file.

NX treats the components in the assembly in an order that does not necessarily represent the order in the assembly structure. This leads to that, in some cases, a specific component (CMP-1) of an assembly (ASY-1) is loaded before the assembly and cloned/saved as the new name (CCMP-1). Thereafter the assembly (ASY-1) that carries that component (CMP-1) is loaded and cloned/saved as the new name (CASY-1). But when the assembly (ASY-1) was loaded it also loaded the component (CMP-1) since that component belongs to the assembly (ASY-1). That component (CMP-1) was already handeled by cloning (to CCMP-1) and will not be addressed again wich leaves us with our cloned assembly (CASY-1) still containing our old component (CMP-1).

That's what we've worked out from the behaviour of cloning. Hope it's clear enough to solve some of your problems. I would not be that surprised if the specification problems also has a solution in this, but that's hard to say without seeing the .clone file.

With best regards,
/Lars