Cancel
Showing results for 
Search instead for 
Did you mean: 

Redefine interpart copy to a different context.

PLM World Member Legend PLM World Member Legend
PLM World Member Legend

Suppose I have a part with some interpart copy features that were defined in the context of a particular assembly.  Now suppose I want to shift that part to a different assembly for some valid reason.  I now wish to continue the design in the context of that different assembly.  That design process may include some additional interpart copies created in that same context.  Now any new interpart copies cannot normally be created until the links to the old assembly are deleted and that is perfectly understandable.  So that means that the original interpart copies either have to have their links broken or be deleted and re-created from scratch.  Now breaking the links is fine if you know those interpart copies are never going to change.  On the other hand, if those inter-part copy links need to remain live then there is no choice but to delete them and start again.  That is a pain because most of the downstream features get messed up or deleted - resulting in extra work to fix.  All that could be avoided if one could redefine an interpart copy to pick a parent part in the new context (assembly).  I can see that a potential issue would exist with multiple interpart copies (temporarily) having different contexts - although maybe one could get around that by having a command to change the context of all the linked features in the part all in one hit.

 

I think that would be a great enhancement.  Would anybody tag onto that if I got an ER sent in to GTAC?

8 REPLIES

Re: Redefine interpart copy to a different context.

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

Hi @chrisstandring,

 

I would absolutely support such enhancement[s].

.....in a very similar situation to this, just yesterday, with using Subtract in assembly, which I discovered, pushed all the inter-part links to the part file I was modifying, BUT, I had to delete those & rethink the approach, because it's a part we use in other assemblies.

Sean Cresswell
Design Manager Streetscape Ltd
Solid Edge 2019 [MP1] Classic [x3 seats]
Windows 10 - Quadro P2000

Re: Redefine interpart copy to a different context.

Valued Contributor
Valued Contributor

Dude Smiley Happy

 

This sounds a lot like WAVE interpart copy functionality avaiable in NX.

You will get my vote for sure.

 

 

Re: Redefine interpart copy to a different context.

Honored Contributor
Honored Contributor

I have exactly the same problem, but I don't use inter part copy for anything. I'm all ordered because I need parts driving other parts. There is no way to make one Sync part drive another Sync part without using more variable links.

 

I make parts within the context of an assembly to that planes and other parts can control the part size.

 

I have yet to find a way of ripping a part out of one drawing and re-use it in another in a way that is faster than re-creating the part. The time cosuming portions of the work are:

Reasigning sketch segment to planes in the new context

Re-linking variable between part and draft

Re-asigning variable names from draft dimensions to variables

Re-drafting the part

 

There are a few parts I have needed to model & draft 100's of times. All the same design, but the size varies in each case based on other parts of the assembly.

 

Because this is very difficult to explain, here is one of my "template" draft & assembly files that I re-size for many jobs.

 

Open model, and move say Plane X2 by 2" and see what happens to the draft.

 

Re: Redefine interpart copy to a different context.

Creator
Creator

We face this problem a lot, and it's time consuming to break the interrelated copy and redefine all related operations, even if it's the same part, position, geometry, all the same!.

It would be a good improvement to redefine inter-party links.

Re: Redefine interpart copy to a different context.

Legend
Legend

@chrisstandring, you just summed up precisely why we do not use that type of interpart copying and linking from assemblies in general.  During development, sure...  well maybe.  Soon as the parts hit production, kill any links to any where used assembly.  Most of our parts go to too many assemblies to let one magical assembly drive it and thereby push changes to other assemblies.

 

@SeanCresswell, Is'nt there an option to have it create the cut in the instance local to that assembly only?  I think the first option should work for you?  Or am I missing something?

 

image.png

 

edit: apologies for my horrible speling...


Those who know me question the assigned user rank.

Re: Redefine interpart copy to a different context.

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

Hi there @bnemec,

 

Yes, agreed,....and using that method is how I then over come the issue.

 

But, that is NOT how the "Subtract" in assembly works. As I found out, it pushes linked operations back down to the part[s], which would be fine, but as in the case I had, where it was one of our library parts, that was used in many assemblies elsewhere, that can't have those features included. [let alone the fact, if they could be included, it would result in a drawing revision needing to be published, for those assemblies affected, and potential client approval]

 

Sean Cresswell
Design Manager Streetscape Ltd
Solid Edge 2019 [MP1] Classic [x3 seats]
Windows 10 - Quadro P2000

Re: Redefine interpart copy to a different context.

Legend
Legend

@SeanCresswell thank you for pointing out, I missed the "Subtract" keyword.  I was unaware that feature existed, probably because we have little use for it since it always edits the part.  Most of our projects are slight changes to existing products or different combination of existing components.  Unless it's a completely new, ground up, product line ~90% of the components in our top level assembly would be what you call "Library parts" 


Those who know me question the assigned user rank.

Re: Redefine interpart copy to a different context.

PLM World Member Legend PLM World Member Legend
PLM World Member Legend

ER 9221029