Finding the location (path within project) of linked component. . .

[CruftMeister]

Preamble: In Fusion, the bulk of my assemblies are made with components linked into the assembly. I tend to reuse components and find this method yields the best results for my designs and workflows. I generally create subfolders within a project to organize the various types of components (e.g. discretes, mechanical, power, archived parts, temporary assemblies, etc) so I are usually end up with a number of sub-folders in a given project.

Question: I was working in an assembly with a number of components linked in from various sub-folders.  I wanted to take one of those linked components used in the assembly and link it into a new assembly, but I wasn't sure in which subfolder that component was stored; getting properties on the component did not give me its path.  So I opened the linked component from within the assembly, however, even with the component file open could not figure out which subfolder in the project I had stored it. 

I was on a flight and in offline mode, so search is disabled.  However, upon my arrival, I reconnected, and searched, but the results still only give me the component, not its location.  I tried looking at the tabs to see if they had the file path, tried looking at the "properties" of the component itself, all to no avail.

I eventually  found it by manually going through each subfolder in the project, but I am hoping someone can tell me a better way to find the storage location of a component - ideally from data within the file itself, e.g. some "get info" function  - or equivalent - that I am missing.

Anyone got an idea on this?

[jeff_strater · Accepted solution]

This is not particularly clever, and there may well be better ways to find this info, but I tend to use Save As to find this out.  If you open the referenced component, then invoke Save As, it shows the whole path to where that component is currently stored:

then, I just cancel the command...

Not the most elegant method, and Fusion should certainly have a better way to do this

Jeff

[CruftMeister]

Hi Jeff,

Clever is not required, workaround is good enough - does the job, thanks!

Art

[Anonymous]

I don't know whether this has been updated and cancelled out but I don't find that this solution works in any means!

Is there anyone else still getting this problem?

Sam

[ahsan.autodesk]

Hi there,

The folder path to the referenced files can be easily viewed from Fusion Team, i.e., Fusion's central workspace on the Cloud. In Fusion's side panel, click on the version number for your specific Assembly. You'll see something like below:

Fusion's Side Panel

Now, click on "Open Details on Web". It'll take you to your Cloud account on Fusion Team, and show you details for your Assembly file. Click on "Overview" to see all the files that are referenced by your Assembly. Then click on the specific referenced file you're interested in. You'll see its Overview now. It'll look something like this:

The top portion will show the folder location for your file. Hope that helps.

[Anonymous]

@Anonymous

edit -> oops parallel post to @ahsan.autodesk

Doesn´t work for me either.

What I do:

1) in the data-panel, search for file name

2) expand the version-button

then I get what I want:

[Anonymous]

You can have a look at my free add-in: LessClicks

Maybe it meets your requirements.

[CruftMeister]

Hi Manfred,

Thanks, this looks really cool, but I'm running Fusion on a Mac so it won't work on my platform.  I do run Altium on Windows, but if I were to run MCAD on Windows I'd just go back to Solidworks.

Regards,

Art

[anna-luise.wokusch]

Hey there,

I used to find out the location in the way that Manfred Steinbach described. Today I discovered that not all folders are given anymore, only the project, when I'm lucky one subfolder. But not the whole filepath anymore. 

This really sucks:-(

Does anyone has a solution for this?

[sales]

One should be able to click on a linked component and see where the component lives in the folder structure, yes? This should be easy folks. Does anyone have an update on this? 

[romeu.pinto]

We really need this something like this

Is this really that dificult to implement?

[romeu.pinto]

Thanks, thats perfect 🙂