Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- 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.
Versions and Branching
christopher_owens
Member Posts: 235 ✭✭
Hello! I didn't see a dedicated discussion to this subject! Of course I am going to try some "what ifs?" using Versions and Branches. I am curious if someone has ultimate control over what gets Merged into a Project. Also what if one designer creates a feature using another feature, while a different designer deletes/modifies that used feature. What happens when either designer does a Merge?? Of course training, communication and collaboration is critical, but the software does what the software is told! (Would people just start "overwriting" each other? Hence the need for Versions and History!)
Tagged:
0
Answers
If i create some features in branch-1 then merged to main and again if i create same feature (with different value) in branch-2 and merged into main.In this case features created in branch-1 updated first and then that features are modified as per branch-2(latest merged branch).
If i created different features in both branches and merging it to main then features created in both branches are added to main work space.
Is there anything to compare in assembly..? motions ..?
The fact that they have rolled out a diff viewer indicates they are making progress towards being able to do conflict resolution. So that's promising.
But meanwhile merge is a booby trap that they really should document properly in their help to make it less so...
There's been a few past discussions on this stuff. Here's one:
https://forum.onshape.com/discussion/comment/1966
https://www.onshape.com/cad-blog/under-the-hood-collaboration?success=true
@ilya_baran You guys plan on implementing merge conflict resolution right? I'm happy to send you a copy of git that implements only Onshapes version of merge for you and your team to use in your day to day development while you guys are thinking about it.... maybe it will motivate you?
This is one of those things that you don't need often but when you do life is utterly miserable if you don't have it.
I see you can Copy the Read Only Version Workspace to a new document. I assume that becomes an active Workspace??
OK after making one of my 5 Documents Inactive, I was able to Copy the Read Only Version Workspace to a new Document, and it is now Active and I am able to modify it.
I had to create a new workspace from that version to export.
This doesn't make sense at all to me: If I release a Version of my document to a client or supplier, I need them to be able to export various formats from that read only version. Otherwise, it is useless as a document sharing mechanism. I will try creating the exports before creating the version, and see if they can be downloaded from there.
NOPE!
I can't even download an exported XT file that is saved in a tab.
How are we supposed to treat Versions as usable file repositories or archives?
For me, I see the potential workflow to be:
-work on a workspace
-save a Version (01A)
-share the document (or, preferably, just 01A) with client with instructions: "you can download STEP or IGES from workspace 01A")
-I continue to work in the new "Main" workspace, incorporating feedback / changes from suppliers and clients
Currently, however, I don't see a way to export / download from a View Only Version of the document.
Indaer -- Aircraft Lifecycle Solutions