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.
Revisions & Configurations inside of Assemblies
When you have an assembly and you make it configurable, you can configure one of your models inside of the assembly that is also configured. For example, we have a tube configuration that is used in multiple locations in a model, and we configure in the assembly which tube configuration appears depending on the options we select from the table. It's a very powerful tool when dealing with configured assemblies.
However, we have hit a bit of a snag. We want to use, going forward, released models when making our assemblies. Because each end product tends to be very customized per customer, we want to make a template document where we start with the basic structure, copy-work-space, and then make changes as needed under the new part number. Having this template would standardize our process (something we couldn't do at all with SolidWorks, because it'd crash on us almost constantly or the configurations would explode on us) and it would make it so we already have 75% of the work done before we even start. These templates are very much doable...with versions.
The moment we try to use released models, we cannot configure them. The only option given is whether it is suppressed or un-suppressed.
My question to the community and Onshape is was this an intentional feature when it comes to releases? I'm asking before I submit an improvement request because I want to understand what led to how its structured right now, whether it is intentional or a "we haven't gotten to it yet" thing (which I completely understand). I just feel that it is disconnected from how Onshape normally handles configurations in assemblies with a blanket absence of that feature once released. If the mindset is "Once released, it shouldn't change unless revised", I understand where that comes from. However, with configurations, you have multiple releases tied to the model. I just would like the option of at least choosing which release to use inside of that model, rather than a disconnect of "you can't change it" once inserted into the assembly.
Thank you for your time