Share

Custom properties

Fusion Manage

Fusion Manage requires a separate license and can be used with Fusion or independently. Learn more.

A custom property is a user-defined data field that extends the standard information tracked for items, workspaces, and other objects in Fusion Manage. Custom properties allow you to capture additional business-specific information beyond the default fields provided by the system. An administrator can create up to 500 custom properties in a hub.

Why use custom properties

Custom properties help you tailor Fusion Manage to match your organization's unique processes and data requirements. You can use custom properties to:

  • Track industry-specific information such as regulatory compliance data or certification requirements.
  • Capture company-specific attributes like internal cost codes or vendor ratings.
  • Add project-related fields such as milestone dates or resource allocations.
  • Extend standard fields with additional details relevant to your workflows.

Property value types

When creating a custom property, you define what type of value it will store. Fusion Manage supports several value types:

  • Text: Single-line or multi-line text entries for descriptions, notes, or codes.
  • Integer: Displays whole numbers without decimals.
  • Float: Displays numbers with decimals.

Where custom properties appear

Custom properties can be added to items in the Components workspace. When you create a custom property it will appear in the Bill of Materials, Properties panel and Properties in the web view for the hub.

Managing custom property values

Administrators control how custom property values are defined and maintained. When an admin creates a custom property, they can decide if the property can be edited by others in the hub or if it's read-only. The property can also be visible or hidden to others in the hub.

Best practices

When implementing custom properties:

  • Use clear, descriptive names that make the property's purpose obvious
  • Avoid creating duplicate properties that track similar information
  • Limit the number of required properties to only essential fields
  • Use picklists instead of free text when possible to maintain data quality
  • Document property definitions and usage guidelines for your team

Was this information helpful?