One student has errors on a shared file that the others do not.

[Andy_Marston]

I have a team of students working on a project where one student is having issues. When she opens the design she gets an error message telling her there are unresolved external components. All the other members of the team open the exact same design without issue. I have attached images of the messages she receives.

[dan.banach]

Hi @Andy_Marston 

Can you confirm that the Inventor assembly and part file(s), are all uploaded in Fusion's Data Panel?

If other students can open the Inventor assembly in Fusion, please ask one of them to Export a .f3d file and share it with the student who can't open the assembly file.

If the issue continues, can you post the Inventor assembly files? 

Thanks,

-Dan

[Andy_Marston]

Hi Dan,

Thanks for getting back to me. The file is a development of an imported design, in other words, a part was downloaded and then the students have added to it in order to create a design for a car for the F1 in Schools competition so the original part is not a component as such. It is in the data panel and saved in the team I have created for my students (thanks to you help!). I can open it and there is no problem for me just this one student - I wondered if there was something I had done wrong in adding her to the project?

I'll get one of them to export and share tomorrow and get back to you.

Many thanks,

Andy

[dan.banach]

Hi @Andy_Marston

It’s strange that just one student can’t open the file.

Coincidentally, I can see that last week you invited ~35 students to your Fusion Team, about half have not finished creating their Autodesk account, and should be able to sign into Fusion. Most of them have not opened the email invitation that should have been sent when you invited them into your Fusion Team / Project.

You can Private Message me the student’s email address, and in the morning (in the US) I can look into her account.

Thanks,

-Dan

[dan.banach · Accepted solution]

To close this post. The issue was due to the role that was set for a folder in a Folder-Level Project.

Thanks to @Andy_Marston for his help in fixing the issue.

-Dan