Rich944
Mechanical
- Feb 8, 2007
- 68
Hi All,
We have an existing NX large assembly of a piece of equipment (say assy1), I need to create another piece of equipment (Say Assy2) that is 90% the same as Assy1. Assy2 needs to be a specific part number which already exists on Teamcenter.
I am trying to find a way to save all of the structure and constraints from Assy1 to Assy2. I have tried doing a 'save as' but doing 'save as' to an existing part number has been disabled for us.
I have tried exporting the named references for the Assy1 NX dataset and importing them to the Assy2 NX dataset, when I open the NX dataset only 5 components out of 119 have imported. I checked all the named references and they are identical.
I have also tried copying the components from the Assy1 assy navigator and pasting into Assy2 assy navigator, however all constraints are then disassociated.
Can anyone think of anything else I can do? If not I will have to bite the bullet and build Assy2 from scratch.
Cheers,
Rich
We have an existing NX large assembly of a piece of equipment (say assy1), I need to create another piece of equipment (Say Assy2) that is 90% the same as Assy1. Assy2 needs to be a specific part number which already exists on Teamcenter.
I am trying to find a way to save all of the structure and constraints from Assy1 to Assy2. I have tried doing a 'save as' but doing 'save as' to an existing part number has been disabled for us.
I have tried exporting the named references for the Assy1 NX dataset and importing them to the Assy2 NX dataset, when I open the NX dataset only 5 components out of 119 have imported. I checked all the named references and they are identical.
I have also tried copying the components from the Assy1 assy navigator and pasting into Assy2 assy navigator, however all constraints are then disassociated.
Can anyone think of anything else I can do? If not I will have to bite the bullet and build Assy2 from scratch.
Cheers,
Rich