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.
How can i make a design change to all my branches in once?
Tony_Chen
Member Posts: 2 ✭
I have a small project which create three branches for same basic model.
Due to some reason the basic model need to change on several locations.
Onshape dosen't allow me to edit on version point unless i restore it. But restore means what i edit become the latest model.
I make a edit in one of branches and then merge to another branch, all the features including what should keep different are merged.
Is there any efficient way to solve situation like that? make a design change to base version then update to all branches in once?
Due to some reason the basic model need to change on several locations.
Onshape dosen't allow me to edit on version point unless i restore it. But restore means what i edit become the latest model.
I make a edit in one of branches and then merge to another branch, all the features including what should keep different are merged.
Is there any efficient way to solve situation like that? make a design change to base version then update to all branches in once?
0
Answers
I suppose this is something that will be handled with configurations in future?
Depends. Branching and the configurations work we're doing are for different purposes. Configurations are going to be primarily for the "I am designing a family of parts" use case (and then, yes, you'll be able to make changes to all configurations at once). Branches are primarily for collaboration and exploring design alternatives. So they'll both have their place (and, for example, doing branching and merging on a Part Studio with multiple configurations will have its uses also).
Thanks for the insight, this scenario is exactly what I'm waiting for.