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
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 Answers
-
Options
stevehess
Moderator, Onshape Employees, Developers Posts: 98 
Hello @tara_miles and thanks for your post. Let me see if I can address some of your concerns:
The Onshape "version" is exactly as you described - a snapshot of the document in time. Versions are designed to be immutable and as such geometry in version can never be changed. This behavior is intended to preserve the design history in a way which allows for reliable reuse of designs and provide traceability to those that need it. A part or assembly in a version can be distributed (shared) with complete confidence that it will never change.
Versions are not intended to behave like Solidworks configurations, although I completely understand why one might assume they are, especially given that Onshape does not (yet) provide a method to create configurations (AKA variants, tabulated designs, design tables, etc). Please stay tuned, I am sure you will like what we are working on. We definitely hear you on this one. Onshape design tables will be awesome.
We have heard from users that "Deleting a version" is desireable. It's a bit tricky especially if a part/assy from that version has been used in another design so we have to be careful. You WILL (soon) be able to clean up the version graph such that the "pile of versions"are not cluttering up the the graph and insert dialogs. Making version "invisible" may be the a stop along the way to what you are asking for. But we hear you, if I make a version (accidentally or otherwise) and no one is referencing it, then let me delete it.
In the meantime, the "create version" icon on the toolbar allow you to quickly make and name a version without opening the version graph. it will also autoname (V1, V2, etc) if that meets your needs. I use it to quickly create the next version, the I let the notifications (the link icon on the tab) system tell me when a new version is available. It works but can be cumbersome in a rapidly evolving design process involving multiple documents.
Finally, you might consider designing in a single compound document during ideation and early prototype. Then use the copy and paste functionality to move the part studio tabs to other documents. It may not meet all your needs but worth investigating.
I hope this helps and welcome your feedback.
Steve Hess \ Onshape Inc.8 -
Options
chrisjh777
Member Posts: 207 ✭✭✭✭
I have learned that, I too, did not comprehend the intent of Onshape "Version".
During development of a complex design, I created a version, thinking that I could delete it later. Big mistake!! My design document now has this unwanted version embedded forever.
I now avoid versions like the plague!!
I realize now that what I should have used is "Branching" where apparently, you have the option of merging branches later as the design progresses. However, try as I may, I could not get my head around the branching philosophy.
I have now adopted a design development approach that involves making multiple tabs (assemblies or part studios with suitable distinguishing nomenclature) of different "versions" of my design. Then, when I am satisfied, simply delete the unwanted tabs. Bit cumbersome but, I am in full control of my design.5 -
Options
brian_brady
Member, Developers Posts: 505 EDU
Any idea on timing of the roll out of OS design tables? I have started preparing for teaching 3D modeling and FEA for the fall semester and want to use OS instead of Creo (due in part to its collaboration capabilities), but creating design tables and configurations based on parameters/variables is a topic I think needs to be covered.stevehess said:
Versions are not intended to behave like Solidworks configurations, although I completely understand why one might assume they are, especially given that Onshape does not (yet) provide a method to create configurations (AKA variants, tabulated designs, design tables, etc). Please stay tuned, I am sure you will like what we are working on. We definitely hear you on this one. Onshape design tables will be awesome.
BTW, OS is a dream come true of sorts for me for teaching solid modeling. I have long wished for a "generic" 3D modeling package that can run on almost any student computer that is easy to learn and whose skills/practices can be transferred to any number of other commercial 3D CAD applications. I don't think my job in a university is to teach which buttons to push on a specific CAD application. It is to teach transferable modeling skills and techniques as well as proper design intent and control. I do plan on using Creo for teaching FEA, as I have not found one on the OS Store that I like and is as easy to use as Creo Simulate.5
Answers
The Onshape "version" is exactly as you described - a snapshot of the document in time. Versions are designed to be immutable and as such geometry in version can never be changed. This behavior is intended to preserve the design history in a way which allows for reliable reuse of designs and provide traceability to those that need it. A part or assembly in a version can be distributed (shared) with complete confidence that it will never change.
Versions are not intended to behave like Solidworks configurations, although I completely understand why one might assume they are, especially given that Onshape does not (yet) provide a method to create configurations (AKA variants, tabulated designs, design tables, etc). Please stay tuned, I am sure you will like what we are working on. We definitely hear you on this one. Onshape design tables will be awesome.
We have heard from users that "Deleting a version" is desireable. It's a bit tricky especially if a part/assy from that version has been used in another design so we have to be careful. You WILL (soon) be able to clean up the version graph such that the "pile of versions"are not cluttering up the the graph and insert dialogs. Making version "invisible" may be the a stop along the way to what you are asking for. But we hear you, if I make a version (accidentally or otherwise) and no one is referencing it, then let me delete it.
In the meantime, the "create version" icon on the toolbar allow you to quickly make and name a version without opening the version graph. it will also autoname (V1, V2, etc) if that meets your needs. I use it to quickly create the next version, the I let the notifications (the link icon on the tab) system tell me when a new version is available. It works but can be cumbersome in a rapidly evolving design process involving multiple documents.
Finally, you might consider designing in a single compound document during ideation and early prototype. Then use the copy and paste functionality to move the part studio tabs to other documents. It may not meet all your needs but worth investigating.
I hope this helps and welcome your feedback.
During development of a complex design, I created a version, thinking that I could delete it later. Big mistake!! My design document now has this unwanted version embedded forever.
I now avoid versions like the plague!!
I realize now that what I should have used is "Branching" where apparently, you have the option of merging branches later as the design progresses. However, try as I may, I could not get my head around the branching philosophy.
I have now adopted a design development approach that involves making multiple tabs (assemblies or part studios with suitable distinguishing nomenclature) of different "versions" of my design. Then, when I am satisfied, simply delete the unwanted tabs. Bit cumbersome but, I am in full control of my design.
BTW, OS is a dream come true of sorts for me for teaching solid modeling. I have long wished for a "generic" 3D modeling package that can run on almost any student computer that is easy to learn and whose skills/practices can be transferred to any number of other commercial 3D CAD applications. I don't think my job in a university is to teach which buttons to push on a specific CAD application. It is to teach transferable modeling skills and techniques as well as proper design intent and control. I do plan on using Creo for teaching FEA, as I have not found one on the OS Store that I like and is as easy to use as Creo Simulate.
As you might imagine, a lot can happen as we roll out new functionality so we don't forecast release dates. Having said that, we definitely understand that design tables and the the related operations are very important to our customers. So please stay tuned......
And great to hear your thoughts on teaching 3D CAD, we completely agree.
Be sure to keep current on our FEA partners in the appstore though. We have some excellent FEA options which you will very useful, especially in an educational environment. Please have an honest look at them look before jumping to Creo.
IR for AS/NZS 1100