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.

What Causes In-Context References to Break?

Zane_MorrisZane_Morris Member Posts: 3

I have a complete assembly, call it Assy1. I want to design a cover/enclosure for some portion of this assembly. Whether or not it was the best workflow (I've since realized it isn't), I utilized the ability to create an in-context part studio to do so. In the newly generated part studio (call is PS1), while in the context of Assy1, I create a transform "copy in place" feature, where I create copy a subset of parts found in Assy1. I did this because 1) I don't necessarily need all the parts found in Assy1 (fasteners, etc.), and 2) having to render all parts in Assy1, or in other words creating my cover part entirely in the context of Assy1 would, increase render times.

After making this transform feature, I exit out of the context of Assy1, and begin creating all features associated with the cover inside of PS1. These features only reference geometry of the copied parts (obviously). About halfway through designing the cover, I realize I need to create copies of a few more parts from Assy1. So, I re-enter the assy context, update my transform "copy in place" feature, then again exit out of this context and continue designing in PS1.

Somewhere between that point and me finishing the design, the in-context references to the assembly break, and I lose access to the Assy1 context within PS1. This means that I can no longer enter into the context of Assy1 and either update the Transform feature, or create any other features that reference the assy. From my understanding, nothing I do inside PS1 can cause these in-context references to break. During the process of designing the cover, changes were made to parts found in Assy1 that I had copied into PS1. I'm not sure if this would have broken anything, but I can't see why this would be the case.

Does anyone know what causes in-context references to break irreparably? Where did I go wrong? Any information would be of great help.

Comments

  • mahirmahir Member, Developers Posts: 1,314 ✭✭✭✭✭

    Copy-enabled link to your doc?

Sign In or Register to comment.