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.
Is there a way to transfer features to another part studio or document?
We have a part studio in a document which is getting more complex than necessary. I can see that a bunch of features for one part are really unrelated to anything else, and are slowing things down. I know I can make a new part studio, derive the critical things which are dependent on the main part studio, and then recreate the detail work in the new part studio.
Are there any short cuts to move the features from one part studio to the other?
Are there any short cuts to move the features from one part studio to the other?
Tagged:
0
Answers
Although that might take a bit of work to not accidentally delete stuff you need as the dependencies only show "one level".
Derive from a version is probably your best bet to help performance while keeping the link, you could derive your part body as well as some reference sketches/geometry (in separate derive features if you need to toggle things on and off separately, that would be the closest to "copying features" but would be slow when updating the version).
Using a context could also make sense in some cases (if the parts end up in the same assembly with the same spatial relation)?
To answer your question, I have not found a way to copy features from one part studio to another.
Sorry, I tried to post this about 30 minutes after the initial question, but for some reason my post was marked as needing approval before it was able to post.
I would totally use this... Just discussed workarounds for this today (applying similar "post processing" steps to several downloaded models)
I would absolutely love that, and not to say I expect every id to perfectly preserve itself every time, I understand that things can get really entangled when working with parametric models, but even in the case of things like reference parameters or other parameters in feature UIs, it saves a lot of time to be able to carry over some of the previously selected options that variables cannot manage.
chadstoltzfus@premiercb.com