Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.

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.

Best practice - Moving branch to new document

Lars_LørupLars_Lørup Member Posts: 2 PRO

I've been working on alternatives to one of our current parts as branches of a part studio. We have gotten to the stage where we would like to move these branches to separate onshape documents.
This is because our working practice is to have a separate onshape document per part and these new parts will coexist with their own new part #. (this setup is probably due to old habits from other softwares, but it's how we decided to structure our files).

Does anyone have any "best practice" on how to move a branch to it's own part studio? I still want to retain the old part studio with the old main branch. My first thought was to copy the onshape document, make the branch the new main and delete other branches in the copied workspace. I could also delete the now obsolete branches from the original part studio. I am not sure if this is the best way forward - curious to hear if others have similar challenges and perhaps thoughts on how to proceed?

Comments

  • Lars_LørupLars_Lørup Member Posts: 2 PRO
    edited September 13

    When you copy a workspace you don't copy the branches/version history. You just copy the state of the current selected branch of when you copy the workspace, without a history tree. This seems to be quite a good solution for my issue, but still open to hear others thoughts.

  • eric_pestyeric_pesty Member Posts: 1,947 PRO

    You can also use the "move to document" option to move a tab to it's own document from the branch you want to "split off". This way the old branch is still there in the old doc but ends with the tab being moved out so you can see the history if you need to…
    The new document will basically be the same as if you had done a "copy workspace".

Sign In or Register to comment.