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.
Adding "HIDE" as an option, when configuring large assemblies

As much as I like the options that Configurations provide, I am wondering if an additional feature can be added other than " Configure Suppression"? I have assemblies, with multiple tree layers. At the lower level assemblies, I have BOM components that I do not need to show. Initially, I used "configurations" which suppressed components I did not want to display on my drawings. However, when trying to sync the BOM with a PLM system, the BOM would end up incomplete due to suppressions. As a solution, "Display State" was used to hide the components. However, the Display State does not propagate through the BOM and I had to recreate the same Display State at every assembly level. To make a long story short, can "Configure Hiding/Display" be added as a feature that could propagate throughout the BOM? Thank you.
Comments
Display States is likely still the best workflow here. They don't propagate through assembly levels like Named Positions or configurations, but when you insert a subassembly, it will match the hide/show state of the subassembly itself. Thus, if your subassemblies are properly hiding parts, when you insert them into the top level those same parts will be hidden, and you can then create a display state of the top level. Then you can show all / toggle between display states at the top level.
And frankly, you have to make the configurations at each level anyways, so hopefully Display states isn't too much more manual. Configuring suppression will always lead to BOM incompleteness, as you noted