Skip to main content

​
Identify the Error

Custom field issues typically present as:
  • A column appears empty even though work items have values in the custom field
  • Editing a column does not persist values back to Polarion
  • The column appears with a read-only indicator when it should be editable
  • Custom field type (number, date, enum) renders as plain text

​
Step 1: Add the Property to the Domain Model

Custom fields must first be declared as properties on the appropriate entity type in your domain model. Each property name maps to a Polarion field: 
domainModelTypes:
  SystemRequirement:
    polarionType: systemRequirement
    properties:
      description: ~
      severity: ~
      priority: ~
      c_myCustomField: ~     # Custom field property
The property name should match the Polarion custom field ID. Polarion custom fields are prefixed with c_ by convention (e.g., c_riskLevel, c_verificationMethod). Confirm the exact field ID in Administration > Work Items > Custom Fields.

​
Step 2: Add the Column to the Sheet Configuration

After adding the property to the domain model, add a corresponding column in your sheet configuration: 
columns:
  c_myCustomField:
    title: "My Custom Field"
    width: 150
For properties on related entities, use the full binding path: 
columns:
  systemRequirements.systemRequirement.c_verificationMethod:
    title: "Verification Method"
    width: 150
diagram

​
Step 3: Verify Type Mapping

Powersheet automatically maps Polarion field types to appropriate data types. If your custom field appears but renders incorrectly, check the type mapping:
Polarion TypeExpected BehaviorCommon Issue
StringText inputRenders correctly by default
IntegerNumeric inputEnsure value is saved as number
Float / CurrencyDecimal inputCheck decimal precision
BooleanCheckboxMust be true/false
Date / DateOnlyDate pickerDate format mismatch
EnumDropdown selectorEnum values must match Polarion

​
Step 4: Check Read-Only Status

If the column appears read-only unexpectedly, verify:
  1. Column-level: The isreadOnly property should be false (default)
  2. Formatter-level: Check if a formatter applies readOnly style
  3. Permission-level: Verify the user has write permissions
  4. System fields: Built-in fields like id and outlineNumber are always read-only
columns:
  c_myCustomField:
    title: "My Custom Field"
    width: 150
    isreadOnly: false        # Explicitly allow editing (this is the default)
If the domain model property name differs from the Polarion custom field ID, use the customFieldName property to establish the mapping explicitly. This is required when you want a user-friendly property name that differs from the Polarion field ID.

​
Step 5: Verify Enum Custom Fields

For enum-type custom fields, the available options are loaded from Polarion. If the dropdown shows no options or incorrect options:
  • Confirm the enum is defined in Polarion for the correct work item type
  • Ensure the polarionType in the domain model matches the work item type that has the enum configured
  • Check that enumValues in the domain model (if specified) matches the Polarion enum option IDs

​
Verification

After making corrections:
  1. Save both the domain model and sheet configuration
  2. Wait for the connection to restart (status returns to Active)
  3. Reload the powersheet document
  4. You should now see the custom field column with correct values, proper editing controls, and successful save operations

​
See Also

Sources: SaveTest.java, MetadataTest.java, Property.java, DataPropertyFactory.java
Source Code
  • SaveTest.java
  • MetadataTest.java
  • Property.java
  • riskmanagement_model.yaml
  • DataPropertyFactory.java