How to export/move libraries, INCLUDING 3D models to another Fusion Hub

[jesper8W75R]

I'm going to move/copy/share  a number of projects to another Fusion Hub, to allow people in different locations to work with the same designs.
This shouldn't be too complex.

I also have a number of components libraries, with around 1200 components, many with 3D models.
I also want to export those, so they're available to everyone in the hub.
This seems a bit more complex.

How do I do this?

[jorge_garcia]

Hi @jesper8W75R ,

I hope you're doing well. For moving the libraries between hubs, the easiest way is to use managed libraries, you'll transfer all of the 3D models and components. The managed library can be reached by both hubs so it's an ideal way to move all of the content over.

For project data you have to use the Online project manager of Fusion and you transfer the project to another hub you are a member of.

Let me know if there's anything else I can do for you.

Best Regards,

[jesper8W75R]

Thank you Jorge, there is absolutely something you can do.

---

For project data you have to use the Online project manager of Fusion and you transfer the project to another hub you are a member of.

You make it sound so easy. But this IS Autodesk Fusion, so I know NOTHING is easy.
And after spending a long time trying to accomplish this, I give up.
I can only copy or move folders within my own project hierarchy, I find no way to copy/move to the Hub that I'm a member of.
Please explain HOW to do this.

[jorge_garcia]

Hi @jesper8W75R ,

Thankfully one of my colleagues has written a helpful article on how to do this.
https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/How-to-transfer-fi...

Let me know if you have any problems following the article.

Best Regards,

[jesper8W75R]

Thank you for the link @jorge_garcia 

The problem is that I HAVE NO transfer option.

From the link you sent, I found the page "Transfer button is missing when transferring projects in Fusion"
But if offers no solution.
1. I'm admin in my own hub
2. I'm Editor in the Project in the destination hub.
3. It's not a system project
4. Destination is a Team Hub
5. The project I wanted to transfer, is a Folder-Level project (more about that later), but it's the same for other projects that are legacy projects.
6. Project is NOT in someone elses Single User Storage

So,  why is the no transfer option???

------

To return to the Folder-Level issue:
Here's two quotes from that page:
"The ability to transfer projects that is a Folder Level Permission type project is currently only available by request. If you have projects that is a Folder Level Permission, and wish to use Project Transfer - Fill out this form here to enable the functionality: Request project transfer. "

"Note: It is only possible to create Folder-Level projects. Creating legacy projects (Open, Closed, Secret) is no longer available."

You see the problem here?
You are enforcing the use of Folder-Level projects. Even asking us to convert old projects to Folder-Level.
BUT you don't support transferring them.

Are you serious?

[jesper8W75R]

As a follow up to this. 

It turned out that I was only added to a project in the destination hub, not in the actual team.
That is solved now, and I can transfer projects (as long as it's legacy projects).
I transferred a bunch of folders with various sub-projects to a legacy project and moved that over.
But, now I've run out of old legacy projects to use as a "transfer truck" to get my folders moved over to the other hub.

WHEN will you update your transfer routines to allow transfering Folder-Level projects, as that's the only thing we can create now.

I'm AGAIN, dead in the tracks by your strange decisions to implements new features, without implementing the tools to actually USE these features.

[jesper8W75R]

@jorge_garcia  ?????

[jorge_garcia]

Hi @jesper8W75R ,

This is a general Fusion issue and not Electronics. I thought I had requested to have this moved to the main Fusion forum.

I'll do that again, since there is nothing else I can do here.

Best Regards,

[jesper8W75R]

@jorge_garcia 

My fault. It WAS moved, and I asked for it to be moved back again, as I don't see how electronic libraries are a common Fusion thing, but ok, projects are.

But, @jorge_garcia instead of moving this back and forth, it would be nice if you would answer the actual questions.

WHY are you enforcing a project policy that is not even supported?

WHEN will this be fixed?

We're dead in the water and cannot contiue development because you've thrown a stick in the wheel with that project-folder sh*t.

[jorge_garcia]

Hi @jesper8W75R ,

If I could answer the questions I would, I honestly don't know the answer to either question. By having the thread moved, the experts in project management would be able to chime in.

I'll see if I can find someone more knowledgeable about this aspect and can offer some guidance. Remember that Fusion is meant to be a platform, the electronics team is just a small part of it. Depending on how you look at it, for better or worse we inherit many of the behaviors of the platform. Hubs and project management are one of those behaviors.

Let me see what I can find out.

Best Regards,

[Andy.Spivey]

//edit - fixed missing link to KB article

Hi @jesper8W75R ( and @jorge_garcia ) ,

Just saw / was directed to this thread by another community member and I should be able to help.

@jesper8W75R , we can get project transfer enabled for folder-level projects for you by filling out some information via this link noted in this article. As to any reasons to the why we need to go this path, I can ask a PM to chime in regarding (I don't know the answer) as needed.  

Once enabled, that will allow you to transfer any remaining Folder-Level projects from the hub in question.

Please let me know if there is anything else I can help with - I will provide the feedback noted above regarding the transfer option not being default enabled for all project types.  Thank you Sir

Best Regards,

-Andy

[jesper8W75R]

Thank you @Andy.Spivey 

I would DEFINITELY want to know why you have basically broken ALL project transfer functionality.
And also WHY it's necessary to fill in a form to be able to transfer projects.

Did you really think this through?
I guess now ALL Fusion users will have to fill in this form, to perform something that worked before, but which YOU BROKE, with the Folder-Level projects.
I find this absolutely mind-blowing.

Now, I'll try fill in the form, and then I'll have to ask my collaborators to do the same, so we can, if we're bloody lucky, get back to how it worked a few weeks ago.

NOT HAPPY!

[prichas]

Hey @jesper8W75R,

I appreciate your frustration. It is our intention to provide you with the tools required to organize your data in the ways that fit your business needs.

The Project Transfer capability was developed long ago, and originally focused on basic file transfer. Fusion has grown a lot more capable since. More advanced permissioning, cross project references, libraries and other capabilities have surpassed what the transfer tool was designed to cover. Right now there are limited options as have been mentioned above in the thread, but we are working on newer tools.

That said, we understand the importance of the workflows you've mentioned and intend to mature other move/copy workflows in the future. We recently ran a research project with customers that have recently used project transfer to help inform our future plans. No pressure, but if you have time, it would be great to connect for 30 minutes to discuss further.

Regards,

Shayne Prichard

Fusion Product Manager

[jesper8W75R]

Thank you for the explanation, Shayne.

I completely understand the need for changes as things evolve.

What annoys me about this, specifically, is that you FORCED the use of Folder-Level projects, BEFORE implementing the ability to transfer these.
I'm sure you can see how this is backwards thinking.

Or, you could have WARNED about this, BEFORE forcing the Folder-Level projects, so we could have created a heap of legacy project to use as transfer vessels, when you broke the functionality.

Now, after filling the the forms and you flipping some switches, the transfer of Folder-Level projects work. For me.
But there is a LOT to wish regarding transfers, way more granularity so folders or files can be transfered, not complete projects.
To transfer a file or folder as it is, I need to create a new project, move the files/folders into that, transfer that project, then reverse the move of the files into the actual project where they belong at the destination hub.
A tedious process.

Thank you for the opportunity to discuss this, but sadly, my experience after several previous meetings with Autodesk is that it would be a waste of time.