Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape, CAD, maker project and design.

First time visiting? Here are some places to start:

  1. Looking for a certain topic? Check out the categories filter or use Search (upper right).
  2. Need support? Ask a question to our Community Support category.
  3. Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
  4. Be respectful, on topic and if you see a problem, Flag it.

If you would like to contact our Community Manager personally, feel free to send a private message or an email.

import assembly into same document but in separated part studios

eric_zhao867eric_zhao867 Member Posts: 5 PRO
hi, 

We have some solidworks assemblies that consist of some customer design parts and some over the shelf parts. Is there a way to import this assembly and parts into the same document, and in the mean time separated the parts into individual part studios?  

The "split into multi documents" option works to some extent. But I would like to have the parts all in the same document, so that I don't have to keep versioning individual parts and update them manually in assembly. 

thanks, 
Tagged:

Comments

  • 3dcad3dcad Member, OS Professional, Mentor Posts: 2,287 PRO
    I don't think that's possible. Can't think of any quick workaround either if you wan't to maintain connection to assembly. If you only need to isolate some parts you could use derive.
    //rami
  • bradley_saulnbradley_sauln Moderator, Onshape Employees, Developers Posts: 241
    edited November 14
    I guess the first question is why do you want/need the parts in their own part studio? For referencing the over the shelf parts into other projects? The answer to this heavily influences the response.

    Quick answer on how to do this:
    If you need parts imported in as their own part studios then export them out of SW as their own part file (or export the sub assemblies). Then import them into an Onshape document. This will give you control over how you want to split up the assembly on import and with our newly introduced replace you can easily swap it at the top level assembly whereas in the past you would just delete and insert.

    Keep in mind, there are limits to what can be done with imports for any system especially if you want the part placement to be positionally accurate to the source assembly.
    Engineer | Adventurer | Tinkerer
    Twitter: @bradleysauln


  • eric_zhao867eric_zhao867 Member Posts: 5 PRO
    Appreciate all the answers. 

    "why do you want/need the parts in their own part studio:"

    For two reasons: 1) these parts are designed individually in solidworks. If they don't have any relationships, it does not make sense to but them in one large part studio. 2) We often have hundreds of different parts, and may run into up to a thousand part counts. Having a thousand parts in one studio, make it very difficult for future editing. 

    "If you need parts imported in as their own part studios then export them out of SW as their own part file". 

    Yes. aware of this method. But it is tedious for hundreds of parts. Just want to know if there is any way more efficient. 

     
  • Jake_RosenfeldJake_Rosenfeld Moderator, Onshape Employees, Developers Posts: 1,092
    @eric_zhao867

    You could import them all as separate documents, and then as you find parts that you need to edit, move those parts into the document containing the top-level assembly:


    No need to move all the parts at once, just move them into the master assembly when you decide one of them needs an edit.
    Jake Rosenfeld - Modeling Team
Sign In or Register to comment.