how to get all objects in an included component move together

[Shan-d-man]

I am using multiple files where I design individual 'things' in their own file, then I have a master file that handles the enclosure and I do all of the layouts between these 'things' there.  I use the insert component capability and select these things from the other files.  In the enclosure project, I then move them around.  That said, I frequently struggle with a move or align operation that only moves some of the included component but not other things and it scatters.  I want to include them as a single component and not position their individual child components individually.

I tried to go into the child component files and create a rigid group, selecting all components in that file.  This does achieve what I want in the parent enclosure project, however, once I create the rigid group, I can no longer move the components around while I am editing the child file.  I tried supressing the rigid group, which allows me to move them, however when I unsuppress it, they move back.  It feels like I have to delete the rigid group and then remember to recreate it again.

The only other way I can think of is to use joints, however using joints is incredibly difficult to work with.  Consider that if you have two objects aligned to each other, you create a joint, you have to hide one object, to select the face of the other, doing that twice to pick two faces, but when you add the joint, the objects move - yes they are touching, but you have to reposition it again.  I have not been able to figure out how to select two components and just say 'keep them together in their current positions related to each other'.

Any suggestions on how to keep being productive managing individual files for a component without restrictions, but when it is included in another design, it is treated as a single component that moves together without all of these issues?

As an example, every component in my design is in a child file.  Notice the one object on the far left - it's blue faceplate did not move back with the component when I aligned it with the left wall.  The main body moved, but the skin stayed where it originally was.  (highlighted the gap)

If I look at the component in its original file, it is together

I am missing some understanding of object relationships and am hoping an expert here can spot what I need to learn and provide some helpful guidance.

[jhackney1972]

Please attach a representative model and clarify what you would like to do with it by component.  I could use one of mine but it would not be as relevant as using yours.

If you do not know how to attach your Fusion 360 model follow these easy steps. Open the model in Fusion 360, select the File menu, then Export and save as a F3D or F3Z file to your hard drive. Then use the Attachments section, of a forum post, to attach it. If needed, ZIP a F3Z file.

[davebYYPCU]

Both of those pics, do not follow your description.

Means that an Assembly File, does not have, bodies and sketch folders, at top of Browser.

You say you are importing Components, if so they will all have the chain link.  Both pics have components without chain links.

Opinion :  If using, Move to Align, then you don’t understand Joints.  Joints work with snap points, not faces.  Generally, Move and Align should not be used in the Layout file.

Need an example file to review your workflow.

Might help…..

[Shan-d-man]

OK, here is my simplest component that shows the issue (see attached).  You can import this into your cloud service, then create a new project, then create a 12"x12" square and extrude it up by 1/2" to mimic a backer board for this component to be 'mounted' on.  Click Insert Component and select the component file you just imported.  You can move it above the backer board and all parts of it stay together.  To reproduce the problem, select Align, then click the bottom of the part (a face), then click the top surface of the board you just created.  This will move the main body to the board, but the text and the posts will be left above in space.  Ideally these should all move together.  I can achieve this by selecting all of them in the original file and creating a rigid group, but doing that means that I am now limited in making small adjustments in that file as no movements are allowed once it is in a rigid group and I need to delete that step, make my moves, recapture the locations, and recreate the rigid groups.

[etfrench]

None of the components in the file have joints between them.  Simplest method would be to create a rigid group in the file, then import it.  Better method would be to create joints between the components.  This will allow you to adjust their relative positions by editing the joints.

Move and Align are very expensive tools to use.  Each and every move and align must be calculated every time a change is made in the file.  This will slow Fusion to a crawl in larger files.  Moves and Aligns are also not parametric, so any change in an objects position won't update the moved objects position.

[davebYYPCU · Accepted solution]

This latest description makes sense.

Importing the file to a new file, and Jointing the component to the base board, does do what you said.

The reason as best I can see, is the grey cylinder component, is Grounded to Parent in the original file, and the other 2 Components are not.

The moveability of these 2 free standing components is transferred across to the new file and does what you complained of.

Ground to Parent all the Components in the source file.  Will let you edit that file with normal behaviours. 

When imported will behave as expected.

Might help... 

[Shan-d-man]

Thank you Dave.  That was very helpful.  I did not have a full understanding of ground to parent and where it is valuable to use.  Your suggestion resolves my issues completely and helps me understand why some components move properly while others don't when I am using sub-assemblies.  Based on your suggestion I did a little homework on the feature and found this blog article that shows this is exactly what the feature was designed for.  Thank you for the time in responding to my post - it was quite helpful.  I marked your post as the answer.