Query Regarding Fusion 360 API: File Extensions for 2D Drawings and Handling Linked Files in Export Script

[Design_HyperPower]

Hello Autodesk Community,

I hope this message finds you well. I am reaching out with a query regarding the Fusion 360 API, particularly related to file extensions for 2D drawings and handling linked files during export.

In the Project Archiver - Mass Export script developed by Patrick Rainsberry, the Fusion 360 API reference manual (https://help.autodesk.com/view/fusion360/ENU/?guid=GUID-7B5A90C8-E94C-48DA-B16B-430729B734DC) is extensively utilized. However, during my exploration of the manual, I was unable to locate any information about file extensions for 2D drawings generated from Fusion 360 parts and assemblies.

In the provided script, different file types for export are defined with the following line of code:

export_extensions = ['.igs', '.step', '.sat', '.smt', '.f3d', '.stl']

I am curious if there exists a hidden file extension specifically for 2D drawings in Fusion 360.

Additionally, I am experiencing an issue with the script when dealing with files containing parts linked to other files. I am seeking guidance on whether there is a method to bypass this issue, allowing the export of files with linked components seamlessly. This scenario also extends to drawing files linked to their original part files.

Concerning the export of drawing files, we are open to DXF or DWG formats, although Fusion 360 lacks a dedicated file extension for drawing files. While the Fusion 360 drawing workspace offers this functionality, I have been unable to find a corresponding API documentation section detailing how to access the export to DWG/DXF feature programmatically.

I would greatly appreciate any insights or assistance from the community or Autodesk support in addressing these concerns.

Thank you in advance for your time and assistance.

Rafael Ong Yiu Engineering Design & Additive Manufacturing Assistant

[BrianEkins]

The API doesn't provide any additional capability regarding files than you see when interactively using Fusion. When you have a file open, you can use the "Export" command to save it locally in various formats. The picture below shows the options when you have a design open that does NOT have any external references. The first option in the list is the f3d format, which is Fusion's native format for parts and assemblies. All other formats are formats that support modeling type of data, and Fusion supports translators that can translate the Fusion design into those formats. 

Below is that dialog when I have a design open with external references. You'll see that f3d is no longer an option and has been replaced with the f3z format. An f3z format is a zip file containing all of the related f3d files and knowledge about how they're related.

If you have a drawing open, the "Export" command is disabled. It's currently not possible to save a drawing locally.

There is also a big difference in how f3d and f3z files behave when saved locally. In addition to the "Export" command, there is also an "Open" command. When you open an f3d file, it opens it within Fusion, but it's like a new file was created that has that content and has never been saved. Saving it will prompt you to specify a location on the cloud. When you open an f3z, Fusion will prompt you during the open process to specify a location on the cloud where it will upload and unpack the f3z and then open the top-most design. All files in the f3z will be re-created. For example, if you have an assembly that referenced a bolt you had created and saved the bolt in a location where you want to maintain your library parts. You might use that same bolt file in many of your assemblies. When you create an f3z of an assembly that references the bolt, the bolt will be included in the f3z file. When you open or upload the f3z, a new bolt file will be created that the assembly will reference. The creation of an f3z creates a set of files completely independent of the original files.

Fusion is designed to work with its own cloud storage. The ability to save and open using the local file system is primarily meant to allow interoperability with other CAD systems, not as a means to save Fusion files locally.