Bug: "Designs inserted from another hub will not be linked" when both designs in same Team and project

[Bjanders]

Like these two posts:

• https://forums.autodesk.com/t5/fusion-360-support/designs-inserted-from-another-hub-will-not-be-link...
• https://forums.autodesk.com/t5/fusion-360-support/design-inserted-from-another-hub-will-not-be-linke...

I'm also getting the "Designs inserted from another hub will not be linked" dialog when inserting a design from the same project in the into another design. Both designs are in the same Team hub and same project. The design I'm inserting into was imported from Single-User Storage (Design A). The design I'm inserting was created after I imported the project to my Team (Design B). 

To test, I created a third design (Design C) in the same project, and when inserting Design B into Design C, I don't have this issues and the Design C is linked in Design B. 

Rephrasing as a list:

1. I was Single-User Storage only (no Team at all created)
2. I created Project 1
3. I created Design A in Project 1
4. I created other designs in Project 1 and inserted them in Design A and they were properly linked
5. I created my first and only Team and transferred all of my projects in Single-User Storage to the Team in the process
6. I created Design B in Project 1 (now in my Team, nothing is in Single-User Storage)
7. I inserted Design B into Design A and get the "Designs inserted from another hub will not be linked" dialog. Design B is copied into Design B, not linked. This must be a bug, right?
8. To test I created Design C in Project 1 and inserted into Design B. Design C is linked in Design B.

[Bjanders]

No comments on this? Is there any way to work around this so I can insert a linked design?

[steve.oliverH3HKZ]

Did you get anywhere with this?

I am facing the same issue with parts clearly in the same hub (sub folder of the folder the part is in) all recently migrated to teams hub from personal. 

I'm assuming some parts just havent migrated over properly but have no idea how to fix it?

Would appreciate any info if you did fix it.

[VaSIMR200]

I was having the same troubles with identical symptoms. Tried removing NMachineSpecificOptions as well as reinstalling the software but to no avail.

The solution was to create a new copy of the Model (Design A in OP's case) and insert Design A into that, deleting/depreciating the old design. Appears something is broken behind the scenes where old designs are not assigned to the new Team Hub. Unsure how this could slip by Autodesk if it's a common thing, but nonetheless. For me, latest F360 on Windows 11.

Hope that helps someone.

[marcus.schluep]

I had also the same issue. I had to deinstall Fusion and manualy remove all files and folder described  in manual clean uninstall of autodesk fuison: https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/How-to-do-a-manual...

After that it was fixed.

[slipperysubs]

Having the same problem on a Mac (Sonoma 14.6.1). Don't relish a reinstall!

[jackha]

@Bjanders exactly the same here... my old transferred files are linked fine. But newly created designs in the new team will raise the above error when inserted in the "old" project.

edit: I also checked the linked issues, but this one is the must useful and it has exact replication steps.

edit: @VaSIMR200 Your solution / workaround works! Just resaving the model solves it.

[urmo.koiv]

Unfortunately "just" resaving a model is not a viable solution. I have hundreds of subassemblies that will not accept new linked designs. That means I have to resave and re-assemble everything from scratch... Only worst outcome could have been losing all my designs, but this is the "next best thing" that could happen during migration. Basically I've lost the ability to continue work on my designs without resaving and rebuilding everything I've done past 6-7 years.