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.
Is there a way to edit or delete a "version"?
BulletEngineering
Member Posts: 24 PRO
When I was introduced to the "version" system, I assumed it would behave somewhat like the SolidWorks Configuration system - as in one could have an assortment of versions that belong in different assemblies. This would also explain why a version of a document is required to insert a part into an assembly. However, the version system instead acts as a cumbersome "snap-shot" system. Any time something isn't working quite right in an assembly, the user has to go back to the main version, make the correction, and make an entirely NEW version. This ends up creating piles of versions within a given part. One can't simply go into one configuration for one assembly and make a small edit. It seems impossible to edit the versions you already have or even delete the endless supply of unneeded versions... It would be ideal if an user could name the version to correlate with a given assembly and then edit that version as necessary. But even if one could delete a version with a mistake in it and replace it with the correct version, the process would be smoother. Am I missing a way to make this more simple?
0
Best Answer
-
3dcad
Member, OS Professional, Mentor Posts: 2,475 PRO
At first version and configurations are 2 completely different beasts. While we are waiting for configurations to be implemented we might exploit version system to provide similar behavior - including problems you mentioned.
What versions stand for is unchangeable snapshot of whole document - if you have ever bumped into broken assembly because some part has changed and doesn't work in certain assembly anymore then you know what unchangeable fixes.
I like to have robust assemblies where things don't brake apart because I forget which part belongs to where but version certainly need some usage improvements. And one of them is very much ability to delete redundant versions which doesn't have strings attached.
You can make changes to versions, just branch a new workspace from any version and you have like a document inside a document that have no affect to each others.
//rami5
Answers
What versions stand for is unchangeable snapshot of whole document - if you have ever bumped into broken assembly because some part has changed and doesn't work in certain assembly anymore then you know what unchangeable fixes.
I like to have robust assemblies where things don't brake apart because I forget which part belongs to where but version certainly need some usage improvements. And one of them is very much ability to delete redundant versions which doesn't have strings attached.
You can make changes to versions, just branch a new workspace from any version and you have like a document inside a document that have no affect to each others.