Polarion to Powersheet Type Mapping The metadata system automatically maps Polarion custom field types to internal data types when processing domain model configurations.
Polarion Type Internal Data Type Notes StringStringPlain text values TextStringMulti-line text content IntegerInt32Whole number values FloatDoubleFloating-point decimal values CurrencyDoubleMonetary values, stored as decimal BooleanBooleanTrue/false values DateDateTimeFull date and time with timezone DateOnlyDateTimeDate without time component TimeOnlyDateTimeTime without date component DurationTimeStringDuration values as formatted string EnumEnum Constrained option set with ID and display label ListCollection Sets scalar to false for multi-value fields
Conversion Rules Primitive Type Conversion Properties defined in the domain model without an explicit type are automatically typed from Polarion metadata:
The metadata system reads the Polarion field type from custom field configuration
The type is mapped to the corresponding internal data type (see table above)
The mapped type determines column display behavior, editing controls, and query operators
Enum Type Conversion Enum properties receive additional metadata beyond the base type:
Property Description Enumeration ID Polarion enum definition identifier Full qualified enum ID Dot-separated scoped identifier Query keys Context keys for loading options (proto, project, polarionType, enumId) Default value Inferred from Polarion or explicit domain model configuration
List Type Conversion When a Polarion field type is a list (collection), the property is marked with scalar: false. This affects:
Aspect Scalar (true) Collection (false) Data binding Single value display Multi-value display Query expansion Direct property access Requires expand clause Column rendering Standard cell Multi-item cell
Each column in Powersheet carries combined type information that determines its rendering and editing behavior:
Type Category Description Column type Overall column behavior type (text, number, date, enum, etc.) Column value type Specific value format within the column type Property type Combined intersection of column type and value type
Built-In Property Types All work item entity types include these automatically typed built-in properties:
Property Type Read-Only objectIdStringYes (primary key) idStringYes titleStringNo projectIdStringYes (foreign key)
Document Entity Read-Only Fields Document entity types have additional create-only and read-only fields:
Property Access moduleFolderCreate-only moduleNameCreate-only titleCreate-only typeCreate-only allowedWITypesCreate-only outlineNumberRead-only
Security and Type Interaction Server-rendered properties (computed fields) interact with the type system:
Configuration Effect on Type serverRender enabledProperty is always non-editable regardless of updatable readable: falseProperty excluded from metadata; not available to client Entity-level read-only Intersected with property-level updatable
Default Value Resolution by Type Type Default Resolution Primitive (String, Int32, etc.) null unless explicit default in domain modelEnum Explicit domain model default > Polarion enumeration default > null Boolean null unless configuredDateTime null unless configured
Complete YAML Example domainModelTypes : UserNeed : polarionType : userNeed properties : title : ~ description : ~ priority : customFieldName : priority storyPoints : customFieldName : c_storyPoints isApproved : customFieldName : c_isApproved targetDate : customFieldName : c_targetDate estimatedEffort : customFieldName : c_estimatedEffort verificationMethod : customFieldName : c_verificationMethod enumValues : - analysis - inspection - test SystemRequirement : polarionType : systemRequirement properties : title : ~ severity : customFieldName : severity relationships : - from : UserNeed to : SystemRequirement cardinality : many-to-many storage : linkedWorkItems linkRole : relates_to direct : name : systemRequirements back : name : userNeeds
In most configurations, you do not need to specify the type property explicitly. Powersheet infers types from Polarion metadata. Only specify type when you need to override automatic detection or when the property is not backed by a Polarion field.
Related Pages
Source Code
MetadataTest.javaprod-powersheet-src/com.nextedy.powersheet.client/ltc-repo/packages/common/types/domain/document.tsQueryDataTest.javaQueryExecutorTest.javaDataPropertyFactory.java 
