Bug: It is impossible to fix a CutPasteBodies that lost its reference

[Anonymous]

If a CutPasteBodies loses its reference to the bodies it is moving, there is no way to edit it to reassociate the bodies. You also can't make a new one except if you're at the end of the timeline; the official justification for making it impossible to create a new one in the middle of the timeline is that "it might break something if you restructure". Unfortunately, the model is *already* broken since my CutPasteBodies lost its reference, so I indeed have to break all downstream features anyway by deleting the CutPasteBodies, so this justification doesn't really make any sense as far as actually protecting me from myself breaking downstream stuff by restructuring.

Another suggestion was made that the answer is to follow Rule #1 religiously. It's fun to say that, but it doesn't actually fix the issue if you are human and make mistakes. I usually do follow it, but sometimes I make the sketch in the wrong component accidentally (which seems to only be fixable by deleting the entire sketch and doing it again?), and sometimes I decide that some part is suddenly complex enough to make into a separate component rather than keep it as a body.

I considered writing a quick extension to try to fix this, but as far as I could tell based on the documentation, you *also* can't edit a CutPasteBodies with the API, though I don't know if I could make a new one in the middle of the timeline with an add-in.

[dd.stork]

I also found myself stuck in this problem. Quoting @Anonymous , I refuse to accept that the solution is to follow Rule#1 since it is not the solution to this problem.

To me it is just lack of a user interface for a specific operation, realizing a kind of loss of history capturing.

Only in case the bodies comes from a Form feature or a single operation after a Sketch, then it is possible to enter Edit mode on these features and copy the contents, and paste into the relocated Form/Sketch features. In other cases it might be a daunting task to recreate the bodies in the new tree structure location.

I would really appreciate a fix on this an similar features which fail to achieve a real history capture: the operations can't be traced back (such as the values used in a Move feature, lost each time the feature is edited)

[TrippyLighting]

---

@dd.stork wrote:

I refuse to accept that the solution is to follow Rule#1 since it is not the solution to this problem.

---

It isn't!

We've reported this problem a long time ago but it does not come up too often. That's probably why it hasn't bubbled to the top of the development teams to-do list.

As a very viable workaround for solid bodies, you can use the boundary fill command in the surface tab to make copies of bodies. That can be edited and you can reselect the body to be copied if the reference is lost.

[dd.stork]

Ok, but we're talking about Cut/Paste (restructuring) and not Copy/Paste bodies. So following your same approach one should then Remove the body used for Boundary Fill, which looks more a temporary workaround.

[Anonymous]

Is there any reference to this bug report so I can track it?

I found myself in the same situation trying to solve missing body for CutPaste operation... was banging my head for a day until I saw this post...

Even if this does not come up often, it is a VERY disrupting to your process, e.i if that happened, you are basically screwed and need to redo your project to fix this...

Fusion should either let do that fix in the middle of the timeline or prevent any other editing that may cause this...

[rick7SXSV]

Unbelievable. It is now 2025 and the issue still exists. 

[andrewLYA7T]

One really has to wonder who is in control of the product roadmap when they can't fix the basics. These core issues cause so many headaches. Please stop building new features and fix what you have! It seems to be creaking. There are many really basic bits of functionality that will make everyone's life when using Fusion 360 easier.