Document.products Property

Parent Object: Document
Defined in namespace "adsk::core" and the header file is <Core/Application/Document.h>

Description

Returns the products associated with this document.

Syntax

"document_var" is a variable referencing a Document object.
# Get the value of the property.
propertyValue = document_var.products
"document_var" Is a variable referencing a Document Object.
#include <Core/Application/Document.h>

// Get the value of the property.
Ptr<Products> propertyValue = document_var->products();
"document_var" Is a variable referencing a Document Object.
// Get the value of the property.
propertyValue = document_var.products;

Property Value

This is a read only property whose value is a Products.

Samples

Name Description
Create document as part, assembly, or hybrid intent.

Demonstrates creates a new document that is either a part, assembly, or hybrid intent.

Before running: Run from Scripts and Add-Ins. This sample may open dialogs or require interactive choices; keep Fusion in the foreground. No open document is required; the script creates a new design (or additional documents) as it runs.

Generate Setup Sheets API Sample

Demonstrates generating the setup sheets for an existing toolpath.

Before running: Run from Scripts and Add-Ins. This sample may open dialogs or require interactive choices; keep Fusion in the foreground. Use a design with CAM data as required by the script. Many CAM samples switch to the MANUFACTURE workspace and may need an existing setup or manufacturing model.

Generate Toolpaths API Sample

Demonstrates generating the toolpaths in the active document.

Before running: Run from Scripts and Add-Ins. This sample may open dialogs or require interactive choices; keep Fusion in the foreground. Use a design with CAM data as required by the script. Many CAM samples switch to the MANUFACTURE workspace and may need an existing setup or manufacturing model.

Post Toolpaths API Sample

Demonstrates posting toolpaths in the active document using an NC program: import a post configuration from the post library, choose which setups or operations to include, set NC program and post parameters, and run NCProgram.postProcess.

Before running: Run from Scripts and Add-Ins with a design that contains at least one CAM setup with toolpaths. The script prompts for what to post (all setups, first setup, or first operation) and optionally opens the NC file when complete. It may offer to switch to the MANUFACTURE workspace.

Version

Introduced in version August 2014