Add fields to connector-harvested technical asset types

Data Integrity Suite

Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2025

You can extend technical asset types that were automatically created by connectors by adding custom fields to capture additional metadata not provided by the connector. This allows you to enhance your technical metadata model with organization-specific information while preserving the core structure from your datasources.

While connector-harvested technical asset types provide comprehensive metadata from your datasources, you may need to capture additional information specific to your organization's governance requirements. Adding custom fields allows you to:

  • Capture business context for technical assets
  • Add governance and compliance information
  • Include organization-specific classifications

To add custom fields to a connector-harvested technical asset type:

  1. Navigate to Configuration > Governance > Technical Assets.
  2. In either the Containment or Inheritance hierarchy view, locate and select the connector-harvested asset type you want to enrich.
  3. Select the Fields tab in the side panel.
  4. Click Create Field to add a new custom field.
  5. Configure the field properties:
    1. Enter a Name for the field.

      Use a clear, descriptive name that indicates the field's purpose.

    2. Select a Field Type appropriate for the data you want to capture. Available field types include:
      • Text: For single-line text values
      • Text Area: For multi-line text content
      • Number: For numeric values
      • Date: For date values
      • Boolean: For true/false values
      • Enumeration: For selecting from predefined values
      • Asset Reference: For linking to other assets
      • URL: For web links
      • Email: For email addresses
    3. For the Requirement setting, note that only Optional is available.
      Note: Custom fields added to connector-harvested asset types can only be optional to prevent conflicts with the harvesting process.
    4. Provide a Description that explains the purpose and expected values for this field.
    5. Assign the field to a Category to group related fields together.
    6. Configure display settings:
      • Display on Table: Determine if and how the field appears in asset listing tables
      • Show in Details Tab: Control visibility on the details page
      • Display in Column: Specify layout positioning
      • Show if Empty: Determine visibility when no value exists
      • Persist in Filters: Keep filter selections across sessions
    7. Configure any type-specific settings for your selected field type.

      For example:

      • For Enumeration fields: Define the list of allowed values
      • For Asset Reference fields: Specify which asset types can be referenced
      • For Number fields: Set minimum/maximum values or decimal precision
  6. Click Save to create the new field.
  7. Arrange the new field in the desired position using drag and drop or the move up/down options.
  8. You can integrate your custom fields with the connector-harvested fields in any order that makes sense for your governance model.
  9. Click Save to apply all changes to the asset type.

The custom field is added to the connector-harvested asset type and will be available for all assets of that type. You can now populate this field with additional metadata when viewing or editing assets.

For a database table asset type harvested by a connector, you might add these custom fields:

  • Data Owner: An asset reference field linking to Person assets.
  • Refresh Frequency: A text field documenting how often the data is updated.
  • Retention Period: A text field describing data retention requirements.

After adding custom fields:

  1. Update your governance policies to include guidance on populating these fields.
  2. Consider creating data quality rules to ensure consistent values.
  3. Train data stewards on the purpose and importance of the new fields.