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.
Renaming configuration ID doesn't update features that uses that config??
I'm just curious why this is a thing, that when you "Edit FeatureScript IDs" of a configuration
, it breaks features that uses that config, because it doesn't update them with new ID.
However, if you rename a variable it updates all features with new name. Isn't it the same thing essentially?
P.S.
This is actually my current work around this limitation: create a variable with old ID, rename it to new ID and delete it.
2
Comments
I'm experiencing this problem today too. The whole point of using feature-history based CAD software is so that you can reference your past work. It's for you to build up your work, otherwise you would just plan everything from the beginning and skipping straight to the CAD engine. So, why is this very useful feature unable to update all references to it, thereby breaking those references?
If you're trying to organize your work better, changing the config var's internal ID completely breaks Onshape's workflow - since you have to use configurations if you want to derive your next parts based on the last one. For this reason, it's a PITA to use because yes, you now have to rename the internal ID manually now or implement unrelated workarounds that unnecessarily cause designing overhead.
If instead configuration variables acted like normal part-studio variables or variable-studio variables, this peculiar pain point would not exist.
Do you mean just for variable configurations? If so I feel ya. The workaround right now is to make a variable at the top of the feature list with the same name, then change it there before changing the config variable name. Not too bad for one or two part studios, but, as you say, a PITA for a lot of part studios.
The Onsherpa | Reach peak Onshape productivity
www.theonsherpa.com