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.
Version Management
brooke_goetsch
Member Posts: 3 ✭
Hi all,
I have a relatively simple assembly to model, less than 10 components. I'm wondering if there is a better way to keep track of this model than what I have done so far.
For some context, the assembly is a model of a 2'x4'x2' fiberglass planter. My company buys this off the shelf, with a few customizations. Upon receipt we make our own changes, drilling holes mainly. The problem is that this base planter is used for two different subassemblies of our overall product. The steps to 'prep' the containers are different depending on the use case, ex. holes will be drilled in different spots.
How I have managed this in the past is creating a two different versions for the container, then referencing them in their relevant subassemblies. This has caused some pain for me as I was not aware that once you version something you cannot edit that version. So now that we have updated some plumbing fittings within the base container assembly (that is later transformed into two other subassemblies for the final product) I have to go through that versioning process again, there are already about 8 different versions.
I'm wondering if there are better ways to manage this so that is not such a hassle when a small part of the base assembly is updated. And especially to minimize clutter. Happy to provide more context as needed, that was kinda confusing lol.
Thank you
I have a relatively simple assembly to model, less than 10 components. I'm wondering if there is a better way to keep track of this model than what I have done so far.
For some context, the assembly is a model of a 2'x4'x2' fiberglass planter. My company buys this off the shelf, with a few customizations. Upon receipt we make our own changes, drilling holes mainly. The problem is that this base planter is used for two different subassemblies of our overall product. The steps to 'prep' the containers are different depending on the use case, ex. holes will be drilled in different spots.
How I have managed this in the past is creating a two different versions for the container, then referencing them in their relevant subassemblies. This has caused some pain for me as I was not aware that once you version something you cannot edit that version. So now that we have updated some plumbing fittings within the base container assembly (that is later transformed into two other subassemblies for the final product) I have to go through that versioning process again, there are already about 8 different versions.
I'm wondering if there are better ways to manage this so that is not such a hassle when a small part of the base assembly is updated. And especially to minimize clutter. Happy to provide more context as needed, that was kinda confusing lol.
Thank you
0
Comments
I don't think versioning is applicable for what you're trying to accomplish for the reasons given in your description. Part configurations will allow separate hole patterns for flexibility and still allow changes. Each configuration will be derived from the purchased item and given its own part number.
Versioning is for keeping milestones in your design process but they are permanently fixed and are not editable.
https://learn.onshape.com/catalog?labels=%5B%22Self-Paced%20Courses%22%5D&values=%5B%22Configurations%22%5D
In this case though, configurations is definitely the best way.