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.
Options
Any way to identify rebuild errors for all configurations at one time?
tim_hess427
Member Posts: 648 ✭✭✭✭
I'm currently working on a model with a fairly large number of configurations. Is there any way to see, at a glance, which configurations have errors? It can be pretty time-consuming to go through all of these different configurations and chase down any problems.
Tagged:
0
Best Answers
-
Options
philip_thomas
Member, Moderator, Onshape Employees, Developers Posts: 1,381 
@tim_hess427 - No! Because that would mean rebuilding ALL configurations (potentially tens of thousands or more) and neither you nor we want that!!
Philip Thomas - Onshape6 -
Options
Jake_Rosenfeld
Moderator, Onshape Employees, Developers Posts: 1,646
Infinite if you have a numerical configuration variable Jake Rosenfeld - Modeling Team5 -
Optionsphilip_thomas
Member, Moderator, Onshape Employees, Developers Posts: 1,381
@tim_hess427 - Actually YES, there is an easy way
Create a dummy assembly and insert an instance of each 'interesting' configuration that you would like to monitor - that way a single window on a (second) monitor is all you need. Philip Thomas - Onshape6
Answers
What about some sort of "debug" function where you could select a limited number of configurations to check on-demand as opposed to checking every time a change to the model is made?
As a work-around, I did notice that I can open multiple browser tabs and keep a different configuration open in each one. I don't keep every configuration open, but did open up a few "test" cases to catch big things early. At some point, I'll still need to manually cycle through each configuration, though.
Create a dummy assembly and insert an instance of each 'interesting' configuration that you would like to monitor - that way a single window on a (second) monitor is all you need.