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.
Revert a part studio in Main to last released version
chris_evans760
Member Posts: 6 PRO
Hi, I'm sure I'm being slow but... I have a Document with a number of collaborators. I had released a number of parts but one of the team has inadvertently since changed the part in Main. There have been lots of other changes, so I can't simply roll the whole Document Main branch back to before the change. How do I simply revert that one Part Studio back to the released version? I can see it (in the version tree and in Release history), and I can even specify the particular release for use in assemblies etc. But I can't get the version in Main back to how it was before. What am I missing? Thanks
0
Best Answer
-
eric_pesty
Member Posts: 2,119 PRO
You can't just revert a single part/part studio as version affect the whole document...
However depending on what happened to the part you might be able to selectively revert some changes. There was a "tips" video about that but I can't find it...
This will not be practical if there a bunch of changes scattered around but if it's only one change (or a bunch in a row), his how you can do this:
- Create a version directly above the last change (micro version) you want to undo (i.e. by right clicking on it), let's call it "End"
- Crate a new branch from this "End" version
- Restore the last good micro version (from the main branch), (we can call it "Start"), to this newly crated version. If you were tying to fix just a single change it would be just below the action you wanted to revert (i.e. the one you created the version from above)
- You can merge this new branch to main and it will undo all the changes contained between "Start" and "End".
Hope that makes sense!
There might be another way of achieving something similar by crating a branch from the "good" point, moving the part studio out to another document, merging that in (so the part studio isn't there anymore), and moving the "good" one back in. I think that might work?0
Answers
However depending on what happened to the part you might be able to selectively revert some changes. There was a "tips" video about that but I can't find it...
This will not be practical if there a bunch of changes scattered around but if it's only one change (or a bunch in a row), his how you can do this:
- Create a version directly above the last change (micro version) you want to undo (i.e. by right clicking on it), let's call it "End"
- Crate a new branch from this "End" version
- Restore the last good micro version (from the main branch), (we can call it "Start"), to this newly crated version. If you were tying to fix just a single change it would be just below the action you wanted to revert (i.e. the one you created the version from above)
- You can merge this new branch to main and it will undo all the changes contained between "Start" and "End".
Hope that makes sense!
There might be another way of achieving something similar by crating a branch from the "good" point, moving the part studio out to another document, merging that in (so the part studio isn't there anymore), and moving the "good" one back in. I think that might work?
Reverting the Part studio as above should only be done if the change was a mistake and should be discarded...
No, you can't just "copy/paste" as the part studio is defined as a series for actions stored in a database rather than a file.
I think the closest to that is the second option I am proposing where you create a branch that has the "good" part studio in it, then move it temporarily to another document and merge that in your main branch.
Then if you go to your temporary document and move it back, you should end up with what you want. You may end up with some broken references but most of them should be ok.
It might help to go over (or refresh your knowledge if have already done so) some of the material related to branching and merging in the training center if you are not comfortable with the process.
Good luck!
There's another method not mentioned here that can revert ALL changes in a single (or multiple) tabs, even if the changes are scattered throughout the history.
-If you don't already have a version at the point in history where the tab is good, create a version there.
-Right click on that version and select "Branch to create workspace". Name it [branch].
-Switch back to the [workspace] (possibly main) where you want to restore it, then right click on [branch] and select "Merge into current workspace". DO NOT CLICK OKAY YET.
-When the dialog comes up, find the tab or tabs that you want to revert. Since you made no changes in the new workspace, the default "Tab merge strategy" will be "Keep [workspace]". You want to change that to "Replace with [branch]" for any tab you want to revert back to that time. Make sure all the tabs you don't want to change are set to "Keep [workspace]".
This thread pre-dates the "selective restore" option, which makes doing this very simple (i.e. allowing to restore a single tab)
Thanks for pointing out Selective Restore. That's even better. I missed the announcement on that one.
It seems like when searching for how to do something in OnShape, I'm quite often find the answer in these helpful forums. But since OnShape is continually improving, sometimes the response that is marked as the answer can becomes somewhat obsolete. It would be nice if there was a mechanism, even in closed discussions, where a moderator could put in a note at the top of the discussion indicating what new features a user might want to look into that are related to the discussion.