About Custom Properties
The Manufacturing Data Model API allows you to extend the Manufacturing Data Model by attaching custom data to the Autodesk Fusion Component/Drawing versions. You can now add metadata, manufacturing, process information or IDs from external systems as custom properties, modify those properties, and query the properties for their values. Custom properties will also be visible natively in various Autodesk Fusion experiences.

What are Property Definition Collections and Property Definitions?
Property Definition Collection
A property definition collection is a group of properties that are managed by an app. Property definition collections give app owners and editors the ability to group & manage property definitions by context. Property definition collections help save time by allowing you to apply the same set of custom properties to multiple Hubs.

Property Definition
A property definition outlines the attributes and behavior for a particular property. Property definition helps you create a structured and consistent way to extend the data model, ensuring that your custom properties align seamlessly with the rest of your data. For instance, if you are adding a custom property called “supplier stock” to a property definition collection, a property definition will include the following:
- Name: This is the identifier for the custom property. It should be unique within a Property Definition Collection.
- Description: Provides a brief explanation of the purpose and use of the custom property. This helps users understand its intended function.
- Specification: Defines the type of data that the custom property can hold. The supported data types include STRING, INTEGER, BOOLEAN, FLOAT, DISTANCE, DENSITY, MASS, VOLUME, and AREA. These types ensure that data follows standard patterns across the Autodesk platform.
- Property Behavior: Property Behavior field is a vital element of the property definition that determines how the property impacts design versions or is only applicable to specific versions. You can choose the right Property Behavior from the options below based on your need.
Standard: These properties are integral to the design, when they are changed, a new version of the design is created.
- Properties that affect the form, fit, or function of a design, if changed, lead to “new version” of the design.
- These properties are applied on a component/drawing at the tipVersion.
- Examples: paint color, and surface finish.
Dynamic: Properties that are only applicable at a specific, historical version of a component.
- Property values can be retroactively updated (overwritten).
- When a design is changed, the current value is copied over to the next design version.
- These properties are applied on a componentVersion/drawingVersion and are carried forward to the subsequent new version.
- Example: supplier cost.
Dynamic at Version: Properties that are only applicable at a specific, historical version of a component.
- Property values can be retroactively updated (overwritten).
- Typically used for “computed” values.
- These properties are applied at a componentVersion/drawingVersion.
- Example: embodied carbon, material lengths.
Timeless: Properties that remain consistent throughout the versions of a component or drawing. Any modifications to attribute value will affect all versions of the component and drawing uniformly.
- Only one value exists at any given time for all versions/revisions.
- Changes in value do not require a design revision.
- These properties are applied to the Component and Drawing (not ComponentVersion).
- Example: ERP ID, Drawing Number, Part Name.
- IsHidden: To specify intent in an application on visibility of a property.
- isReadOnly: To specify intent in an application to enable or disable ability to modify a property’s value.
- IsArchived: To archive a property value.
- ShouldCopy: Specifies expected behavior for the property on document data management operation like ‘copy’ in Autodesk authoring apps. Setting it to ‘true’ will copy the property along to the new document on such operations.
Note: isHidden and isReadOnly are metadata fields. Changing attributes of these fields won’t affect the properties present on the component/drawing.
Use Property Definition Collections and Property Definitions on your Design & Make Data
Link Collection(s) to Hub(s)
To enable end users to assign values to the custom properties in the property definition collection, the hub admin will need to link the property definition collection to a Hub from your App. Linking a property definition collection to a Hub is a one-time operation. Once linked, users with ‘write’ access to the Hub can assign values to custom properties on components/drawings.

Set/clear property value(s) on Components/Drawings
You can use custom properties to save your custom metadata and associate that data with a particular version of a Component or Drawing. Some examples might include:
- Setting a value on “Vendor cost” property to a version of a component.
- Setting a value on “Surface Texture” property to a component.
- Setting a value on “Approver” property to a version of a drawing.
- Clearing the value on “Vendor cost” property on a version of a component.
Learn more
To learn about creating a property definition collection, property definitions, linking a collection to a user hub and assigning, or clearing custom property values on a componentVersion or DrawingVersion in the API Reference section.