Duplicating Assemblies with Copy Geometry features

[JWayman]

Hello,
I have an assembly with a Skeleton. In the Skeleton are a couple of
Published Geom features. In a couple of the parts within the assembly, there
are External Copy Geometry features.
I would like to do a 'save as' on the whole assembly and the relevant
drawings. I can make the 'Save As' work, except for one thing: The ECG
features still refer to the original skeleton, before the Save As operation.
This leads to much cursing as I attempt to unravel the one set of
relationships and replace them with another.
Am I missing something? Is there a config option to change the External Copy
Geometry references to the new skeleton whenever I do a Save As? Or doe
Pro/E do the easy bit whilst leaving me to do all the hard work?

I have my fingers crossed for the desired answer, but I fear it is more in
hope than expectation...

WF2, M220

Thanks,





This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[bjensen]

Without editing each external copy geom feature I haven't found a way to change what they reference. One trick I have used to get around this is to copy the whole assemby off to another disk. Then Rename the parts that ext. coy geom point to while they are in session. Then you can do a save as for the rest of the parts that you want to give new identities to. After all of that you can save the new assembly back to your database. It can be tedious if the ext. copy geom points to a lot of different parts. That's one reason I always try to keep my copy geom features pointing to skeletons.

[ptc-187142]

One way I've gotten around the problem (after doing the duplicate or save as on everything including the skeleton) is in each of the files that have copy geom references back to the original skeleton I will add a new copy geom reference (which has to be created inside the top level asm) to each of those files, after that I will open each of the files, move the new copy geom feature right under the first one (or the old incorrect one if that's easier to think of it as) in the model tree and then redefine whatever's connected to the old one onto the new one. After that you can delete the old copy geom feature and be on your merry way. It's really not that time consuming unless you have a huge list of files to recreate that copy geom for.

mb

[dgallup]

I have always found it easier to use the file/rename functionality with the RENAME IN SESSION option checked rather than the file/save a copy functionality for this very reason. You can very easily control all the references and only rename those items which you want to duplicate while keeping common items common. Once you have everything renamed that you want to rename then just save the top level drawing or assembly and you have you new version without touching any existing objects on disk.

I have posted this about a thousand times in various user group boards, etc. but I seem to be about the only one who does it. It really is easy and painless.

[mkelley]

You are NOT the only one who does it this way - Renaming In-Session Objects RULES...!

In Reply to David Gallup:

I have always found it easier to use the file/rename functionality with the RENAME IN SESSION option checked rather than the file/save a copy functionality for this very reason. You can very easily control all the references and only rename those items which you want to duplicate while keeping common items common. Once you have everything renamed that you want to rename then just save the top level drawing or assembly and you have you new version without touching any existing objects on disk.

I have posted this about a thousand times in various user group boards, etc. but I seem to be about the only one who does it. It really is easy and painless.

[daniel.garcia]

We use File/Rename a lot too.
Don't forget you can rename anything in memory, not just the current model/drawing
Best regards

Daniel García

Mark Kelley <mark.kelley@ssd.loral.com> escribió:

>You are NOT the only one who does it this way - Renaming In-Session
>Objects RULES...!
>
> In Reply to David Gallup:
>I have always found it easier to use the file/rename functionality with
>the RENAME IN SESSION option checked rather than the file/save a copy
>functionality for this very reason. You can very easily control all
>the references and only rename those items which you want to duplicate
>while keeping common items common. Once you have everything renamed
>that you want to rename then just save the top level drawing or
>assembly and you have you new version without touching any existing
>objects on disk.
>I have posted this about a thousand times in various user group boards,
>etc. but I seem to be about the only one who does it. It really is
>easy and painless.
>
>
>-----End Original Message-----