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.
Options
Force a workspace to update Library Version?
Sometimes old workspaces in old documents don't get updated for some time or at all, but I want to work in there again with the latest feature set. For example I'm in one that still doesn't have thin extrudes and face blends.
If I were to try to merge it into a workspace that had been updated it would let me know about a library version mismatch and prompt an update, but how do I force it to update without a merge?
If I were to try to merge it into a workspace that had been updated it would let me know about a library version mismatch and prompt an update, but how do I force it to update without a merge?
0
Answers
You could version the workspace, then branch it again. This will let you update the new branch. Might not be an option for you if it is a public feature and your trying not to notify everyone of a false update. But then again, we have the option to publish now so that may fix that issue?
Learn more about the Gospel of Christ ( Here )
CADSharp - We make custom features and integrated Onshape apps! Learn How to FeatureScript Here 🔴
The Onsherpa | Reach peak Onshape productivity
www.theonsherpa.com
Perhaps I misunderstood. Updating a workspace to the latest Onshape version right?
Learn more about the Gospel of Christ ( Here )
CADSharp - We make custom features and integrated Onshape apps! Learn How to FeatureScript Here 🔴
https://thesmoothcut.com/
The Onsherpa | Reach peak Onshape productivity
www.theonsherpa.com
The Onsherpa | Reach peak Onshape productivity
www.theonsherpa.com
chadstoltzfus@premiercb.com
The "version/derived manager that works across documents" is exactly what I'd like to see in Onshape's core functionality. So that the "update all" button (or a separate checkbox) literally updates all (even derived parts coming from outside the current document), not just the items located in the current document.
Thank you! This worked perfectly.
Trashing and restoring didn't work for me FYI :/
I just trashed and restored a document, and branches didn't get updated. Merging with mismatched versions is really really really painful.
I think the move might be to delete branch workspaces immediately after they are merged back to main. And if they were never merged, the idea probably died and the workspace can still be deleted. Then there is nothing to update except the Main workspace. Every time I open an old document now I go through its version graph and do this.
It only takes a day (if you hit the wrong part of the 3 week cycle) for one branch to become out of sync. Then it makes merging much more complicated. And as mentioned in another thread, with workspace protection on it’s even worse. This is quickly becoming a top issue for my company.
Is this still true for documents with Branches? We're having challenges merging branches. With many people on a team, it's hard to keep people out of a document for a scheduled update that never seems to happen when it says it will, and Trash/Restore didn't seem to do the trick for branches.