Create custom semantic type fields - Precisely Data Integrity Suite

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
2026

Create custom semantic type fields tailored to your organization's data governance requirements. The field creation process involves selecting a data type, configuring basic properties, setting validation rules, and defining display options.

Custom semantic type fields allow you to extend the default field set with properties specific to your organization's data governance requirements. Each workspace can define its own set of custom fields, which become available for assignment to all semantic types in that workspace.

  1. Go to Configuration > Catalog > Semantic Type Fields.
  2. Click the Create Field button.
    The Create Field dialog opens with a data type selection panel on the left.
  3. Select a Data Type from the left panel.
  4. Configure basic field properties:
    1. Field Name: Enter the display name for the field (e.g., "PII", "Product Code").
    2. API Name: The programmatic identifier for the field used in API calls and integrations. This is typically auto-generated from the Field Name.
    3. Requirement: Select whether the field is Required or Optional for the selected asset type.
    4. Description (optional): Provide a description of the field's purpose and usage.
  5. Configure Value Selection & Validation options based on the selected data type.

    For detailed information about data type-specific properties, see Supported data types for semantic type fields.

  6. Configure Display Options to control how the field appears in the user interface.

    Display Options include:

    • Show in list: When enabled, the field appears in the list view grid.
    • Column Width (Optional): Specifies the width of the column when displayed in the grid.
    • Show in details page: When enabled, the field displays in the details panel.
    • Display in column: When enabled, the field is shown as a column in the grid view.
    • Show if empty: When enabled, the field displays even when it has no value.
    • Editable in UI: When enabled, users can edit the field value in the user interface.
    • Persist in filters: When enabled, the field can be used as a filter criterion and the filter selection persists across sessions.
  7. Click Create Field to save the field.
    The new field becomes available for assignment to semantic types in your workspace.
    Note: Custom semantic type fields can be edited at any time using the Edit action. All properties on custom fields are editable after creation, except for the Data type and API name. This allows you to modify field definitions to meet changing governance requirements while maintaining the field's programmatic identity.

Supported data types for semantic type fields

Semantic type fields support several data types, each with specific configuration options. When you create or edit a semantic type field, the available properties depend on which data type you select. Each data type offers unique configuration options in the Value Selection & Validation section.
Data type Description Configuration options
Boolean A true or false value with customizable labels for each option.
  • Label for first option: The display label for the true value (e.g., "True", "Yes", "Enabled"). This label appears in the UI when the boolean field is set to true.
  • Label for second option: The display label for the false value (e.g., "False", "No", "Disabled"). This label appears in the UI when the boolean field is set to false.
  • Default value (optional): Select the default boolean value when creating new instances. You can set the default to true, false, or leave it unset.
Date A date value without time component. Default value (optional): Select a default date value for new instances using the calendar picker. The date format is DD MMM YYYY (e.g., 15 Jan 2024).
Date with Time A date and time value with timestamp information. Default value (optional): Select a default date and time value for new instances using the calendar and time picker. The format is DD MMM YYYY - hh:mm (e.g., 15 Jan 2024 - 14:30).
Decimal A numeric value with decimal precision.
  • Minimum value (optional): The minimum numeric value allowed for the field.
  • Maximum value (optional): The maximum numeric value allowed for the field.
  • Decimal places (optional): The number of decimal places to display and validate. For example, setting this to 2 restricts values to two decimal places (e.g., 10.25).
  • Default value (optional): The default decimal value assigned when creating new instances.
JSON A JSON-formatted text value for complex data structures.
  • No validation options: JSON fields do not have type-specific validation properties in the Value Selection & Validation section. The UI displays "No options available for this field type" message. Configure display options as needed.
Link A URL or hyperlink reference.
  • Link name default value (optional): The default display text for the link.
  • URL default value (optional): The default URL for the link. Must start with https:// or http://.
List A collection of values.
  • Select list: Configure the list of available values for selection.
  • Allow multiple selections: When enabled (Yes), users can select multiple values from the list. When disabled (No), only a single value can be selected.
  • Default value (optional): Select a default value from the configured list.
Integer A whole number value with optional minimum, maximum, and increment constraints.
  • Minimum value (optional): The minimum numeric value allowed for the field.
  • Maximum value (optional): The maximum numeric value allowed for the field.
  • Default value (optional): The default numeric value assigned when creating new instances.
  • Increment (optional): The increment step for numeric fields, used when incrementing or decrementing values in the UI.
Reference List A reference to values from another list or catalog.
  • Reference configuration: Configure the reference source and mapping for the reference list values.
  • Display item list: When enabled (True), the reference list values are displayed as a list in the UI. When disabled (False), values are displayed in a different format (e.g., dropdown or search field).
  • Default value (optional): Select a default value from the referenced source.
Text (Simple Text) Plain text with optional validation pattern and maximum length.
  • Validation pattern (optional): A regular expression pattern to validate field values. For example, [A-Z]{2}\d{3} validates a 5-character product code with 2 uppercase letters followed by 3 digits.
  • Maximum length (optional): The maximum number of characters allowed for the text field.
  • Default value (optional): A default text value assigned when creating new instances. For HTML/Richtext fields, the default value field includes a rich text editor with formatting options including font selection, text styling (Bold, Italic, Underline), text alignment, link insertion, code blocks, and additional formatting tools.
Text (HTML/Richtext) Formatted text with HTML or richtext markup support.
Tag A tag or label value for categorization. Tag Type: Select the type or category of tags available for this field. This controls which predefined tags users can select from.