linking to components from other assemblies

[Anonymous]

Hi,

Note that I understand everything is a component in Fusion but I'm calling things assemblies and parts in this post just to distinguish between a component which as an assembly, and components which are just parts within it, otherwise I will drive myself mad trying to write this. Also note that I have followed rule #1 before replying about that.

I have created project A with a multi levelled test assembly to get a feel for how Fusion works with linked documents, with several parts and a sub-assy in each, and have got on okay so far with that.

Now I created another project B to see how Fusion works with reusing some existing assys and parts from project A in a different project, and.... I just cannot figure out how to do this.

After struggling with this for a while I read that you can't do this in your single user storage, so I created a team for myself, and then moved my projects there.

I still can't see a way to add components from project A straight into project B, so I then made an empty assembly  in Project B and browsed in the data panel to one of the assys in project A, and right clicked 'insert into current design'.  I get a warning 'Designs inserted from another Hub will not be linked' which only gives me the option to copy it over, which I don't want to do as I want to retain the link to the original so I don't have duplicates of the same parts. I also don't know what a 'Hub' is. Is that the same as the team?

When I view the other project in the data panel I can't seem to find a way to see or access the contents of an assembly, ie where a component contains multiple parts. Can you only insert an entire assembly from another project unless you model every part as separate top level components?

Thanks,
Peter

[TrippyLighting]

I am assuming that you are using a subscription version because I believe a team hub is no possible in the free version (?). So when you click into the upper left corner in Fusion 360 a little window opens to show you your hubs. Here's mine:

"Team Trippy" is my Fusion Team hub. The others above I've been invited to by other users.

The one below in Single-User Storage is where a lot of my "old' legacy data resided before I moved it over to the team hub. Anyway, all of those are hubs. In your case, there is probably one in Single-User Storage and on in FUiosn Team.

In order to link components, they all have to be in one hub.

[TrippyLighting · Accepted solution]

A component or assembly that is located in the data panel can be linked into any other assembly as long as they are in the same hub.

A component that as designed within an assembly and does not reside in its own file in the data panel can be "derived" from that assembly into another assembly.

 

[Anonymous]

Hi Peter thanks for the reply. I am on the free package but I do have a team setup that I created with the onboarding link a few days ago (I called it the same name as my single user storage):

Both of my projects are in that hub:

So here I've got a component open from the 'mate' project, and the components listed from 'assy test' in the data panel:

Now when I right click on one of those and insert into current design I get this error:

...but from what you are saying this would only occur if they are in different hubs, but they (as far as I can tell) are in the same hub.  On the A360 web page for my team, they are both listed:

I'm very confused !

Also the other reply you said about internal components being able to be inserted as derived, is that a link to the original still, or a duplicate?

Many thanks,

Pete.

[Anonymous]

I tried creating some more assys in my team hub, and this seems to work, so I think maybe Fusion is confused with those other projects being moved over from single user storage - going to contact support about that. Here is a derived part inserted from another project - I'm assuming that the curvy arrow represents a linked/derived component (I realise I accidentally derived the body rather than the component in that image, but that worked also). I also checked that this derived component updates from the original, so I think that's sorted. Thanks 🙂

Pete.