Derive Function does not retain grouped bodies

[garrett.glaser]

I often use the Derive function to push discrete portions of assemblies to CNC, and I create groups of bodies for clarity when the CNC programmer is laying out parts. All of that file structure disappears when I derive the components and all the bodies are lumped into one file in no discernible order. I know I can turn everything into components, but often that means re-organizing things I have already organized. Is it possible to have the bodies "file structure" transfer into derived files?

[jhackney1972 · Accepted solution]

Probably the best way to get this done is to Create a Single Component for every group of bodies you want to preserve.  Once you have the component in the Browser, select the bodies you want grouped, highlight them and then left click drag them from their position in the Browser to the new component.  When you Derive the component into another model, the bodies group, under the Component, will be preserved.

[hamid.sh.]

Maybe I haven't understood your problem correctly, but as far as I can tell if you Derive components (select components from Browser and not just bodies from view) file structure is preserved:

[garrett.glaser]

That is what I ended up doing, converting all my groups of bodies into components, which is fine, but another added step to my workflow. My workflow and output does not necessitate converting bodies to components on a granular level (I mean, I guess it does now!), and since Fusion has the function/feature of grouping bodies, it does not seem unreasonable for those groups to carry through when deriving a component. I mean, even being able to sort the list of bodies by alpha-numeric order would be a huge help as it shuffles everything into whatever original logic the bodies were created in. 

Thanks for chiming in!

[garrett.glaser]

Components and nested component assemblies derive fine, but any groups I have created of non-component-ized bodies (inside the bodies folder) revert back to a single level bodies folder with all the bodies inside in no discernible order. It is not a big issue, just something I have run into that is increasing my number of steps in my workflow.

[garrett.glaser]

One thing that still does not seem to carry through with the solution is any re-ordering of bodies. If I name bodies according to some logic of the piece and manually re-order them inside the bodies folder of the component, the bodies folder in the derived component reverts to their original (I assume order of creation) order. for someone who loves giving parts letters and numbers it is quite distressing on a spiritual level!