Ability to moving files between projects - Is there news yet? :-)

[harry.doldersum]

I've been trying to move some files to other project files - which isn't working for me - and I noticed a number of messages, that this is functionality that would be implemented in a future update.

Is there any news on progress?  Not that it's a hold point for us - it's merely for better "house keeping" in our folders. 🙂

FYI, I did find & tried the archive export / import method, as described here on the forum, but I'm probably doing something silly wrong... the file appeared empty. Never mind, I'd prefer to wait for the proper functionality, then. But if someone could update me on progress on that point, I'd appreciate it. 🙂

[charegb · Accepted solution]

Hi @harry.doldersum

Yes, we are still working on this. However we have been making smaller improvements as we work towards the full solution.

Today you are blocked from moving items when relationships exist because we don't allow design relationships across project boundaries. What you can do is - if you have an assembly and a set of parts that are related to each other, move them to a sub folder inside the original project and then move the folder to another project. Since all the relationships are contained in the folder, there is no cross project dependency so the move will succeed.

Thanks

Bankim

[harry.doldersum]

Hi @charegb,

Thanks for your response - moving the folder, as you suggested, was just what I needed.

Much appreciated!

[Anonymous]

The big problem is models with multiple drawings. There is no workaround to move these without breaking things. You can export a drawing, then import it into a different project and it brings the model along with it. But when you have multiple drawings, you end up with a unique model instance for each drawing.

The ability to export/import an entire folder would be an acceptable workaround, but as far as I know, that is not possible today.

[harry.doldersum]

Hi @Anonymous,

Actually, I was able to move folders with components, assemblies & their respective 2D drawings - one folder at the time.  For me, that was just was I was looking for.

I should note, maybe, that this only works from within the browser, that opens up through the top link that you get in the Fusion 360 left side file browser - this then opens up "myhub.autodesk360.com/ ... long url ....".

As far as I could check, all links appear intact...

Hope this helps?

[Anonymous]

@harry.doldersum That works for some, but not all of my folders. When it fails, I just get a red banner across the top of the page saying the operation failed, but no explanation why it failed.

[charegb]

Improving that error is definitely in the backlog.

Usually you will see this error in one of 2 cases:

1)  One of the files in the folder is tagged as in use by someone. This can happen if Fusion crashed when you had a file open. You can check the files in the Fusion data panel by expanding on the i next to it file to see if its in use.

2) One of the designs in the folder has a reference to something outside the folder. i.e. The relationships in the folder are not self contained.

Thanks,

Bankim

[Anonymous]

1. Not opened and not in use.

2. No references outside of the folder. However, one of the differences between a folder that moved and one that didn't is that the one that didn't move has some hardware imported from McMaster-Carr. Maybe Fusion/A360 is treating this as an outside reference.

[Anonymous]

I have a folder that contains all the relationships but I still can't move it to a different project.

The only pop-up menu options are Rename and Archive. Move seems not available. Any idea?

Tom

[charegb]

Hi Tom

Those options show up for Projects. You need to go 1 level deeper to folders inside a project and the move options should be available.

Thanks,

Bankim

[eric]

Has the ability to copy files between projects been implemented yet?

It must be embarrassing to not be able to write a simple recursive copy function.  I mean, just walk the tree an exec a copy on each child.

As a programmer of 35 years, I can tell you there are quite a few giggles in the programming community about the inability to do a simple recursive copy of a file.

[TrippyLighting]

As a cloud platform Fusion 360 does not store data in a simple file.

Trying to get other people to do something for you by intimidating or embarrassing them publicly on a forum is the most surefire way not to get them to help you at all!

[harry.doldersum]

Hi @charegb,

First of all: Happy New Year.  

Then, I'd just like to briefly check with you if there has been further progress on the ability to use models between projects. In the recent Fusion updates, I'm still being slapped an error when I try to see if this works already - and as our post is now roughly some 14 months ago, I just figured I'd ask. 🙂

FYI: Customers who read about Fusion, would like to be invited to "their project", so they could review the models in development & help us with comments. So, we more or less set up shop in that fashion - by preparing for this by assigning different project folders for the customers & suppliers where this applies. But this choice is now beginning to bite us back a bit: we're now in a phase where we'd need to copy some libraries we prepared to each of those different project folders (in order to be able to use them) - or step away from the project folders (& inviting people to them) all together. 

Hence, we'd like an update on the development - see where we are...?  Hope you can provide some insights.

Thanks & cheers,

Harry.

[Anonymous]

I would also like to know if there has been any progress on this.

At the top level, ALL of my projects use folders. I accidentally created a new folder in the wrong project and started working. With the replies above I should be able to move it, but I'm getting the same errors.

Is the issue due to having too many folders or files?

Withing the main folder I have my top level assemblies and a parts folder that itself has folders for different types of parts.

BTW I have around 100 different parts.

[Anonymous]

Why not simply add a feature that will permit an object to be migrated to a different hierarchy. If it is used in two hierarchies, offer to copy one of the objects. The problem is particularly bad for newbies I suspect who get started with Fusion 360 and don't have any ideas or strategies for structuring their folders and drawings. Then when they start to wise up they have a big mess to clean up and no way to get it done. Why not offer maybe to merge two projects together which would then give people the possibility of at least combining all of their projects and sorting them back out that way?