Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.

First time visiting? Here are some places to start:
  1. Looking for a certain topic? Check out the categories filter or use Search (upper right).
  2. Need support? Ask a question to our Community Support category.
  3. Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
  4. 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.

Way to change an existing Sketch into a Derived Sketch?

Corvin_BollCorvin_Boll Member Posts: 12 PRO

I built up a fairly complex part studio. Now we've decided we want to keep the master sketches in a separate tab and have them as derived objects in the original part studio. Is there any way to do this without breaking every dependency and essentially having to rebuild the part studio from the sketches onward?

Comments

  • Rhett_RobinsonRhett_Robinson Member Posts: 126 PRO

    As far as I am aware, this is not possible in the part studio if the part was not already derived. This would be a really interesting/nice to have workflow since it would add to the agility we enjoy in Onshape.

  • S1monS1mon Member Posts: 2,957 PRO

    I wish there was a more automated way to do this.

    What I have done is make a copy of the part studio tab, in one I delete the dependent features - this becomes your master. In the other, I derive the features I need from the master, and then slowly and carefully redo references and delete the now redundant driving features in the second tab. In theory, the new(ish) repair mode should help with this process, but I would recommend having two windows open: one a version from before this surgery, and the other your current workspace. You'll want to be able to hide/show things and carefully query sketch constraints, etc.

    Depending on how carefully you manage your references, this process can be relatively ok. That said, I'm currently working on a part studio with 500+ features that I wish I had split up sooner.

  • Corvin_BollCorvin_Boll Member Posts: 12 PRO

    That's unfortunate. I was hoping there might be a way to duplicate the Studio and then replace the Sketch in one with the Derived version from the other, but I can't figure out a way that would keep the dependencies intact. I would still need to go through all of the dependent sketches, features, etc. and manually change them to reference the identical new sketch entities.

    I'm still deciding whether that would even be easier than rebuilding everything. Especially replacing the broken "projected" constraints in sketches downstream. That's always a pain because the things you need to select will be underneath the sketch entities you want to reattach them to. I've wasted time fixing broken sketch constraints in the past when I should have just started over.

  • Corvin_BollCorvin_Boll Member Posts: 12 PRO

    Thanks, it's helpful to get some insight into how someone else has managed this process! Hopefully at some point we can get a "Send sketch to new part studio and derive" option. I wonder if that is already an improvement request.

  • _anton_anton Member, Onshape Employees Posts: 410

    I found one:

    Please vote on that. :D

    NB, there are multiple possible asks:

    1. Take out one sketch, replace it with a derived, remap the references.
    2. Take out one part.
    3. General replace-this-feature-with-this-other-feature.

    2 and 3 are highly complex and, IMO, ill-defined. 1 is your request.

  • S1monS1mon Member Posts: 2,957 PRO

    @_anton

    I almost feel like writing a more explicit version of #1 as an IR. I don't think I've seen one like that.

  • _anton_anton Member, Onshape Employees Posts: 410

    @S1mon Makes sense, that one was the closest I could find.

  • Corvin_BollCorvin_Boll Member Posts: 12 PRO

    Yeah, I don't know how realistic #2 and #3 are, and that might be why the IR hasn't seen any action since 2018. Making a clearer and more attainable request for just #1 might get better results.

Sign In or Register to comment.