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.
Released configurations - how?!
Olly_Collett
Member Posts: 2 ✭
Hello,
I am having an issue with configured parts / assemblies once released.
The first example is a configured assembly. This assembly has a child assembly that is also configured, with the configuration of the child assembly being a configured parameter of the parent.
To give further context. this is a 'dressed' door assembly with the 'fabrication' as a child. The side door dressed configuration calls for the side door fabricated configuration (amongst other components), the back door dressed configuration calls for the back door fabricated configuration.
The configured fabricated assemblies have been released. When using to 'change to version' function in the dressed assembly to replace the unreleased fabricated door with the released version - all seems good to start with, however when changing configuration the dressed assembly no longer changes the configuration of the fabricated assembly. Ie the back door dressed assembly now has the side door fabricated assembly in it.
Any ideas on how to solve this? Do you have to have two copies of the child in the parent and control their suppression instead? When coming to do the drawings this would double the effort so I'd like to avoid it if possible.
The second example is a harness with two installed positions. Both are physically the same, and thus have the same part number, but their representation in CAD needs to be different driven by the configuration. In this instance the ability to change the configuration of the harness in the parent assembly is lost all together and only the default remains.
Is there something I am missing here? Having two part numbers is not possible and it is critical to show the routing correct in both instances.
Thank you very much for any help!
Answers
The trick is to set the child to be the version containing the release instead of the released item itself. The the BOM will pick it up as a revision. It does require all the configuration of the child to be released in a single release (so they are all in the same version).
For harnesses there isn't really a good option if you need assemblies… The only way you can achieve a released item with configuration that shares a PN is to create it as a composite part (instead of an assembly) and set the "exclude from properties" option for the configuration input.