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.

How to handle broken references when modifications to a part studio cause named parts to be renamed

james_howard360james_howard360 Member Posts: 24 PRO
Working in a part studio with 3 parts whose geometry is interdependent. All part are used as derived parts in other part studios and in assemblies of the same document. A named part that we'll call 12345 needs modifications that involve split and boolean operations. On boolean, OnShape creates a new part called 'Part 2', and 12345 is lost. No big deal, I can rename it, but then everywhere 12345 was used is a broken reference. Renaming 'Part 2' back to 12345 does not fix the references. How can I tell OnShape to keep the reference, or how can I quickly update it across several other part studios and assemblies?

Answers

  • konstantin_shiriazdanovkonstantin_shiriazdanov Member Posts: 1,213 ✭✭✭✭✭
    edited January 9
    This Assign identity feature may help. Though I don't know if it works with part names, but at least it works for automatic substitution of assembly references when you change part selection in the identity feature. It's what @lana gave me when I argued that I needed a persistent identity container, so this is probably some intermediate solution to this problem from OS.
  • ilya_baranilya_baran Onshape Employees, Developers, HDM Posts: 1,101
    It may be possible to change the order of parts in the boolean so that 12345 is not lost -- for a boolean union, the part identity stays with the first part selected.
    Ilya Baran \ Director, Architecture and FeatureScript \ Onshape Inc
  • S1monS1mon Member Posts: 356 PRO
    @ilya_baran

    This concept of ID being driven by the order of the references is one that I've known for so long I almost forget that I had to learn it. It was painfully true when using surfacing in Pro/E, and there are similar issues in Solidworks and Onshape. It seems like something that should be more emphasized in training and documentation. In a perfect world you don't really have to think about it, but the reality is that feature trees blow up when you make changes. If you don't have the right mental model of what's going on internally, it's easy to do things that are very "brittle".

    In general, I've learned to try and keep all of my references to a minimum and make them to the most immutable thing that makes sense for capturing design intent.
  • Evan_ReeseEvan_Reese Member Posts: 1,133 PRO
    in this case I agree that just re-ordering the boolean queries, but wow I didn't know about the Assign identity feature! It seems really powerful, and maybe a little dangerous if used willy-nilly. I tried it out and got some cool results, but also strange ones too. For example, If I assign a new ID to a sketch curve, then try to extrude it, I can't anymore because the extrude feature can't find the sketch plane. I did, however, get ruled surface working for both, and a split across the resulting face doesn't fail when I switch between them. This could open up some cool options for me.
    Evan Reese / Principal and Industrial Designer with Ovyl
    Website: ovyl.io
Sign In or Register to comment.