How to move parts between tabs?

sergio_p_

Hi,

I've imported several parts to an new document, and every imported file is translated to a new Part Studio. Is there a way to move every imported part to a different Part Studio? I meant, it will be easy to manage if I have only two part studios, one for the specific parts being modeled by me and other for the imported parts.

Regards

lougallo

@Sergio_P_ Currently we do not have a way to do this but we have an improvement logged.  I have added you to this.  

philip_thomas

@Sergio_P_  hello. There is a simple workaround. Insert into an assembly the instance(s) of each part that you would like in a single part studio. Next, translate that assembly to parasolid and then retranslate back to Onshape selecting the 'flatten' option. Voila!

philip_thomas

NEW FUNCTIONALITY - YOU CAN NOW DO THIS!

IN-CONTEXT.

1) Insert all the parts you want in one part studio to an assembly
2) Create a new part studio FROM the assembly (in context)
2) Use 'transform/copy' to make copies of all the parts in the assembly
3) Boom!

billy2

Watched the webinar "When Should I Use In-Context Vs. Derived Vs. A Multi-Part Studio?", nicely done.

The answer to my question why would you want to copy parts in-context? weldments.

lougallo

@Sergio_P_ Currently we do not have a way to do this but we have an improvement logged.  I have added you to this.  

sergio_p_

Thanks!

philip_thomas

@Sergio_P_  hello. There is a simple workaround. Insert into an assembly the instance(s) of each part that you would like in a single part studio. Next, translate that assembly to parasolid and then retranslate back to Onshape selecting the 'flatten' option. Voila!

nathan_gf

I tried to find the improvement to add myself too, but I couldn't find it.  Can you add me as well?  This would be very helpful. 

philip_thomas

NEW FUNCTIONALITY - YOU CAN NOW DO THIS!

IN-CONTEXT.

1) Insert all the parts you want in one part studio to an assembly
2) Create a new part studio FROM the assembly (in context)
2) Use 'transform/copy' to make copies of all the parts in the assembly
3) Boom!

brucebartlett

That's awesome @philip_thomas, I hadn't thought to try the transform to get parts into the part studio from the ghost assy, I have been using the derived command but this may also come in handy. Can you then delete the original part tabs?

philip_thomas

@brucebartlett - i haven't tried that workflow, but i can say that in almost every case, 'In-context' replaces derived and for performance reasons, is FAR preferable!

billy2

philip-

Tried this workflow and it worked like a charm.

-trying to get back to the original part studio (with features) was a bit confusing.
-updating copied part studio requires an update to context. This could be handy.

-Moved this part studio to another document but lost incontext and all associativity.

This is interesting, not sure if it's useful. It's a handy way to scatter parts all over an assembly and make it difficult to follow. Do you have a use case for doing this?

I just registered for your webinar on this subject, looking forward to it.

philip_thomas

@billy2 - thank you and your feedback will be added to my webinar material.
The workflow you may be looking for is 'parting out' (separating parts from a multi-part part studio) - we are working on it

billy2

Watched the webinar "When Should I Use In-Context Vs. Derived Vs. A Multi-Part Studio?", nicely done.

The answer to my question why would you want to copy parts in-context? weldments.

philip_thomas

@billy2 - Thank you for attending my webinar - I hope you found it useful
I think you're saying that you got your question answered - if not, please let me know.
I just asked one of the developers your question about loosing the Context when moving a Part Studio to a new Document.
He said that scenario would be supported in the future - although not likely in 2017 as we have a very long list of new functionality we want to get out this year before circling back to this.

michael3424

@philip_thomas - I certainly found your webinar useful, even an eye opener.  Comparing the 3 approaches was a great way focus on the pros/cons of each.  As usual, it was a bit too fast for me to follow in detail, so I'm waiting for the video to be available to do some more study.

billy2

Here's the link to to Philip's video:

"When Should I Use In-Context Vs. Derived Vs. A Multi-Part Studio?"

 Philip you've answered all my questions, thanks

rogier_van_vugt

In the past 6 years has a better solution been developed to combine two imported parts?

NeilCooke

rogier_van_vugt said:

In the past 6 years has a better solution been developed to combine two imported parts?

What's wrong with the Derived feature?