Data Types - Nextedy Documentation

This reference covers every supported data type, its storage format, display behavior, and OData mapping for API access.

risksheet.json column Polarion Field OData API
type: “text”	---->	String / Text	—>	Edm.String
type: “int”	---->	Integer	—>	Edm.Int64
type: “float”	---->	Float	—>	Edm.Double
type: “boolean”	---->	Boolean	—>	Edm.Boolean
type: “date”	---->	Date / DateOnly	—>	Edm.Date
type: “datetime”	---->	Date	—>	Edm.DateTimeOff.
type: “time”	---->	Date / TimeOnly	—>	Edm.DateTimeOff.
type: “currency”	---->	Currency / BigDec	—>	Edm.Decimal
type: “rating”	---->	Integer	—>	Edm.Int32
type: “duration”	---->	DurationTime	—>	Edm.String
type: “enum:id”	---->	Enum Option	—>	Edm.String
type: “multiEnum”	---->	List<EnumOption>	—>	Edm.String

Data Type Summary

Type Identifier	OData EDM Type	Storage Precision	Editable	Notes
`text`	`Edm.String`	Unlimited string	Yes	Rich text converted to plain text for display
`int`	`Edm.Int64`	64-bit integer	Yes	Interchangeable with `rating`
`float`	`Edm.Double`	Double precision	Yes	Standard floating-point
`boolean`	`Edm.Boolean`	True/False	Yes	Renders as checkbox
`date`	`Edm.Date`	Date only	Yes	Format: `yyyy-MM-dd`
`datetime`	`Edm.DateTimeOffset`	Date and time	Yes	Full timestamp with timezone
`time`	`Edm.DateTimeOffset`	Time only	Yes	Format: `hh:mm:ss`
`currency`	`Edm.Decimal`	BigDecimal	Yes	Full decimal precision for financial data
`rating`	`Edm.Int32`	32-bit integer	Yes	Interchangeable with `int`; used for risk scales
`duration`	`Edm.String`	String-encoded	Yes	Polarion DurationTime format
`enum`	`Edm.String`	Enum option ID	Yes	Single selection from enumeration
`multiEnum`	`Edm.String`	Colon-separated IDs	Yes	Multiple selection from enumeration

When you omit the type property on a column, Risksheet infers the type from the Polarion field’s native type. Explicitly setting type allows you to override the display behavior — for example, displaying a string field as a date column or an integer field as an enum.

Text Type

The text type displays string and rich text content. Rich text fields from Polarion are automatically converted to plain text for grid display. Links embedded in content are processed for proper rendering.

Property	Value
Type identifier	`text`
OData type	`Edm.String`
Default for	Polarion `String` and `Text` fields
Fallback type	Any unrecognized column type defaults to `text`
Rich text handling	Stripped to plain text; links auto-processed
Multi-line	Enabled by default (`multiLine: true`)
Word wrap	Enabled by default (`wordWrap: true`)

{
  "id": "description",
  "binding": "description",
  "header": "Description",
  "type": "text",
  "width": 300
}

Any column type not explicitly recognized by Risksheet defaults to text (Edm.String). This provides graceful degradation for custom or future column types and means that mistyping a type identifier will not cause errors — the column will simply render as a plain text field.

Integer Type

The int type stores whole numbers as 64-bit integers. It is functionally interchangeable with the rating type at the storage level, though rating is semantically intended for risk assessment scales and maps to a 32-bit integer in OData.

Property	Value
Type identifier	`int`
OData type	`Edm.Int64`
Precision	64-bit signed integer
Interchangeable with	`rating`
String parsing	Converts string representations to integers automatically
Backing fields	Polarion Integer, String (auto-parsed), Float (truncated)

{
  "id": "priority",
  "binding": "priority",
  "header": "Priority",
  "type": "int",
  "width": 80
}

Use int for general-purpose numeric fields like priority, count, or sequence number. Use rating when the column represents a risk assessment parameter that references a named rating scale in the ratings configuration section.

Float Type

The float type stores decimal numbers using double-precision floating-point representation. It handles conversion between numeric types and parses string representations automatically.

Property	Value
Type identifier	`float`
OData type	`Edm.Double`
Precision	IEEE 754 double precision
String parsing	Converts string representations to floating-point
Backing fields	Polarion Float, Integer, String (auto-parsed)

{
  "id": "riskScore",
  "binding": "riskScore",
  "header": "Risk Score",
  "type": "float",
  "width": 100
}

Boolean Type

The boolean type handles true/false values with automatic conversion between string representations ("true" / "false") and native Boolean objects. In the grid, boolean columns render as checkboxes.

Property	Value
Type identifier	`boolean`
OData type	`Edm.Boolean`
Display	Checkbox
String conversion	`"true"` and `"false"` strings accepted
Null handling	Null values display as unchecked

{
  "id": "mitigated",
  "binding": "mitigated",
  "header": "Mitigated",
  "type": "boolean",
  "width": 80
}

Date Type

The date type stores date-only values without a time component. Values are formatted in ISO 8601 format (yyyy-MM-dd). The system automatically converts between Polarion Date types, Java Date/Calendar objects, and ISO string representations.

Property	Value
Type identifier	`date`
OData type	`Edm.Date`
Format	`yyyy-MM-dd`
Time component	None (date only)
Conversion	Handles Polarion Date, Java Date/Calendar, and ISO strings
Culture sensitivity	Display format affected by `global.culture` setting

{
  "id": "dueDate",
  "binding": "dueDate",
  "header": "Due Date",
  "type": "date",
  "width": 120
}

DateTime Type

The datetime type stores a full timestamp including both date and time components with timezone offset. This is the type to use when you need to capture both the date and the time of day.

Property	Value
Type identifier	`datetime`
OData type	`Edm.DateTimeOffset`
Format	Full date-time with timezone offset
Conversion	Handles Polarion Date, Java Date/Calendar, and ISO strings
Culture sensitivity	Display format affected by `global.culture` setting

{
  "id": "lastModified",
  "binding": "updated",
  "header": "Last Modified",
  "type": "datetime",
  "width": 160,
  "readOnly": true
}

Time Type

The time type stores time-only values without a date component. Values display in hh:mm:ss format. Note that despite storing only a time component, this type maps to Edm.DateTimeOffset in OData.

Property	Value
Type identifier	`time`
OData type	`Edm.DateTimeOffset`
Format	`hh:mm:ss`
Date component	None (time only)
Conversion	Handles Polarion Date, Java Date/Calendar, and ISO strings

{
  "id": "analysisTime",
  "binding": "analysisTime",
  "header": "Analysis Time",
  "type": "time",
  "width": 100
}

All three temporal types (date, datetime, time) map to OData date-related types. The time type maps to Edm.DateTimeOffset despite storing only a time component. External integrations consuming the OData feed should account for this mapping and parse the value accordingly.

Currency Type

The currency type uses BigDecimal precision for financial data, wrapping values in Polarion’s Currency type for accurate decimal calculations without floating-point rounding errors.

Property	Value
Type identifier	`currency`
OData type	`Edm.Decimal`
Precision	BigDecimal (arbitrary precision)
Polarion storage	Currency type wrapper
Conversion	Handles numeric values and string representations
Use case	Cost tracking, financial risk quantification

{
  "id": "mitigationCost",
  "binding": "mitigationCost",
  "header": "Mitigation Cost ($)",
  "type": "currency",
  "width": 120
}

Use currency when exact decimal precision matters (financial data, cost tracking). Use float for general-purpose decimal values where minor floating-point rounding is acceptable (risk scores, percentages).

Rating Type

The rating type is semantically designed for risk assessment scales such as severity, occurrence, and detection ratings. It is functionally similar to int but maps to a 32-bit integer in OData and is commonly used with the colon syntax to reference a named rating scale.

Property	Value
Type identifier	`rating` or `rating:scaleId`
OData type	`Edm.Int32`
Precision	32-bit signed integer
Interchangeable with	`int`
Typical use	Risk parameter scales (1-10, 1-5) per ISO 26262, ISO 14971
Colon syntax	References a named scale in the `ratings` section

{
  "id": "sev",
  "binding": "sev",
  "header": "Severity (S)",
  "type": "rating:severity",
  "width": 80
}

When a rating column references a named scale, Risksheet loads the scale definitions from the ratings section of your risksheet.json:

{
  "ratings": {
    "severity": [
      { "id": "1", "name": "Negligible", "description": "No injury" },
      { "id": "2", "name": "Minor", "description": "Light injury" },
      { "id": "3", "name": "Moderate", "description": "Moderate injury" },
      { "id": "4", "name": "Significant", "description": "Severe injury" },
      { "id": "5", "name": "Catastrophic", "description": "Life-threatening" }
    ]
  }
}

See Enum Columns for detailed enumeration and rating configuration patterns.

Duration Type

The duration type handles time span values. Duration values can be backed by Polarion’s DurationTime type, or stored as numeric values (integers or floats) representing duration units. Despite representing time-based data, duration values are stored and transmitted as strings in OData.

Property	Value
Type identifier	`duration`
OData type	`Edm.String`
Storage	String-encoded Polarion DurationTime
Backing fields	DurationTime, Integer, or Float fields
Parsing	Uses Polarion’s DurationTime format
Example values	`"1d 4h"`, `"2h 30m"`

{
  "id": "effortEstimate",
  "binding": "effortEstimate",
  "header": "Effort Estimate",
  "type": "duration",
  "width": 120
}

Duration is stored as Edm.String in OData despite being time-based. External integrations should parse the duration string format rather than expecting a native time type. If you need numeric duration values for calculations, consider using int or float types with a convention for the duration unit (e.g., hours).

Enum Type

The enum type displays single-selection enumeration fields. The system uses enum option IDs for most fields, with the exception of the status field which displays the human-readable enum name. Enum columns support Polarion native enum fields, string fields, and integer fields as backing storage.

Property	Value
Type identifier	`enum` or `enum:enumerationId`
OData type	`Edm.String`
Selection	Single value
Display	Enum option ID (name for `status` field only)
Colon syntax	`enum:enumerationId` references a named enum set
Backing fields	Native enum, string, or integer Polarion fields

{
  "id": "riskCategory",
  "binding": "riskCategory",
  "header": "Risk Category",
  "type": "enum:riskCategory",
  "width": 140
}

The enum set is defined in the enums section of risksheet.json:

{
  "enums": {
    "riskCategory": [
      { "id": "safety", "name": "Safety Risk" },
      { "id": "security", "name": "Security Risk" },
      { "id": "performance", "name": "Performance Risk" },
      { "id": "compliance", "name": "Compliance Risk" }
    ]
  }
}

For complete enum configuration including dependent enums and icon display, see Enum Columns.

Multi-Enum Type

The multiEnum type allows selecting multiple enumeration values from a dropdown. It works with native Polarion multi-enum List fields as well as string fields containing comma-separated enum IDs. Blank options are automatically filtered out.

Property	Value
Type identifier	`multiEnum` or `multiEnum:enumerationId`
OData type	`Edm.String`
Selection	Multiple values
Colon syntax	`multiEnum:enumerationId` references a named enum set
Backing fields	Polarion List of enum options or comma-separated strings
Blank handling	Blank options automatically filtered out

{
  "id": "affectedSystems",
  "binding": "affectedSystems",
  "header": "Affected Systems",
  "type": "multiEnum:affectedSystems",
  "width": 200
}

WorkItem enum fields require specific type syntax matching the XML custom field definition. For example, type: "multiEnum:@NoIDWorkItems[workpackage]" references a WorkItem enum with a specific configuration. Upstream and downstream WorkItem enum fields have limited support compared to row item properties.

For multi-select enum configuration details, see Multi-Enum Columns.

Type Prefix Extraction and Colon Syntax

Risksheet column types support a colon-separated syntax where the portion before the first colon identifies the base type, and the portion after carries additional configuration parameters. This is how columns reference their enumeration, rating, or reference definitions.

Pattern	Base Type	Parameter	Purpose
`enum:severity`	`enum`	`severity`	References the `severity` enum definition
`rating:occurrence`	`rating`	`occurrence`	References the `occurrence` rating scale
`multiEnum:affectedSystems`	`multiEnum`	`affectedSystems`	References the `affectedSystems` enum set
`ref:requirement`	`ref`	`requirement`	References a linked item type
`multiEnum:@NoIDWorkItems[type]`	`multiEnum`	`@NoIDWorkItems[type]`	References a WorkItem enum field

The type parser extracts the prefix before the first colon to determine the base data type, then passes the remainder as configuration context. This means enum:severity and enum:riskCategory are both enum base type columns but reference different enumeration definitions.

{
  "columns": [
    {
      "id": "sev",
      "binding": "sev",
      "header": "Severity (S)",
      "type": "rating:severity"
    },
    {
      "id": "occ",
      "binding": "occ",
      "header": "Occurrence (O)",
      "type": "rating:occurrence"
    },
    {
      "id": "det",
      "binding": "det",
      "header": "Detection (D)",
      "type": "rating:detection"
    }
  ],
  "ratings": {
    "severity": [
      { "id": "1", "name": "Negligible" },
      { "id": "2", "name": "Minor" },
      { "id": "3", "name": "Moderate" },
      { "id": "4", "name": "Significant" },
      { "id": "5", "name": "Catastrophic" }
    ],
    "occurrence": [
      { "id": "1", "name": "Remote" },
      { "id": "2", "name": "Low" },
      { "id": "3", "name": "Moderate" },
      { "id": "4", "name": "High" },
      { "id": "5", "name": "Very High" }
    ],
    "detection": [
      { "id": "1", "name": "Almost Certain" },
      { "id": "2", "name": "High" },
      { "id": "3", "name": "Moderate" },
      { "id": "4", "name": "Low" },
      { "id": "5", "name": "Undetectable" }
    ]
  }
}

User Reference Type

User reference columns have special handling for Polarion user assignment fields. Read-only user columns display the user ID as a string. Editable user columns manage the work item’s assignees collection, supporting single-user assignment.

Property	Value
Type identifier	`ref` (with user field context)
Read-only display	User ID as string
Editable behavior	Clears all assignees, adds specified user
Assignment limit	Single-user assignment only

Editable user reference columns clear all existing assignees and add the specified user. Only single-user assignment is supported through the Risksheet grid interface. If you need multi-user assignment, manage assignees through the Polarion native work item form.

Read-Only System Fields

Certain Polarion system fields are always read-only regardless of column configuration. Risksheet silently ignores save attempts to these protected fields.

System Field	Read-Only Reason
`id`	Work item identity — cannot be changed
`status`	Controlled by workflow transitions
`type`	Work item type — immutable after creation
`project`	Project assignment — immutable
`outlineNumber`	Document structure — managed by Polarion
`author`	Auto-set by configuration manager
`resolution`	Auto-set by configuration manager
`created`	Timestamp — auto-set at creation
`updated`	Timestamp — auto-set on modification

Columns also become automatically read-only when:

The formula property is set (calculated columns)
The serverRender property is set (server-rendered columns)
The column references a cross-project item (reference columns)
User permissions deny modification of the bound field

See System Fields for the complete list of system-level bindings.

OData Type Mapping Reference

The complete mapping between Risksheet column type identifiers and OData EDM primitive types for API access:

Risksheet Type	OData EDM Type	Notes
`text`	`Edm.String`	Default for unrecognized types
`string`	`Edm.String`	Alias for `text`
`multiEnum`	`Edm.String`	Colon-separated IDs in string
`rating`	`Edm.Int32`	32-bit integer for risk scales
`int`	`Edm.Int64`	64-bit integer for general numbers
`float`	`Edm.Double`	Double precision floating-point
`boolean`	`Edm.Boolean`	True/false
`currency`	`Edm.Decimal`	BigDecimal for financial precision
`date`	`Edm.Date`	Date only, no time component
`datetime`	`Edm.DateTimeOffset`	Full timestamp with timezone
`time`	`Edm.DateTimeOffset`	Time only, but mapped as DateTimeOffset
`duration`	`Edm.String`	String-encoded despite being time-based

See OData API Endpoints for information on consuming Risksheet data through the OData protocol.

Complete Example

A complete risksheet.json column configuration demonstrating multiple data types in a realistic FMEA scenario:

{
  "columns": [
    {
      "id": "failureMode",
      "binding": "title",
      "header": "Failure Mode",
      "type": "text",
      "width": 250,
      "level": 1
    },
    {
      "id": "riskCategory",
      "binding": "riskCategory",
      "header": "Category",
      "type": "enum:riskCategory",
      "width": 130,
      "level": 2
    },
    {
      "id": "sev",
      "binding": "sev",
      "header": "Severity (S)",
      "type": "rating:severity",
      "width": 80,
      "level": 2
    },
    {
      "id": "occ",
      "binding": "occ",
      "header": "Occurrence (O)",
      "type": "rating:occurrence",
      "width": 80,
      "level": 2
    },
    {
      "id": "det",
      "binding": "det",
      "header": "Detection (D)",
      "type": "rating:detection",
      "width": 80,
      "level": 2
    },
    {
      "id": "rpn",
      "binding": "rpn",
      "header": "RPN",
      "type": "int",
      "width": 70,
      "formula": "commonRpn",
      "readOnly": true,
      "level": 2
    },
    {
      "id": "mitigated",
      "binding": "mitigated",
      "header": "Mitigated",
      "type": "boolean",
      "width": 80,
      "level": 2
    },
    {
      "id": "dueDate",
      "binding": "dueDate",
      "header": "Due Date",
      "type": "date",
      "width": 120,
      "level": 2
    },
    {
      "id": "mitigationCost",
      "binding": "mitigationCost",
      "header": "Cost ($)",
      "type": "currency",
      "width": 100,
      "level": 2
    },
    {
      "id": "affectedSystems",
      "binding": "affectedSystems",
      "header": "Affected Systems",
      "type": "multiEnum:affectedSystems",
      "width": 180,
      "level": 2
    },
    {
      "id": "effortEstimate",
      "binding": "effortEstimate",
      "header": "Effort",
      "type": "duration",
      "width": 100,
      "level": 2
    }
  ],
  "formulas": {
    "commonRpn": "function(info){ var value = info.item['occ']*info.item['det']*info.item['sev']; return value?value:null;}"
  },
  "ratings": {
    "severity": [
      { "id": "1", "name": "Negligible" },
      { "id": "2", "name": "Minor" },
      { "id": "3", "name": "Moderate" },
      { "id": "4", "name": "Significant" },
      { "id": "5", "name": "Catastrophic" }
    ],
    "occurrence": [
      { "id": "1", "name": "Remote" },
      { "id": "2", "name": "Low" },
      { "id": "3", "name": "Moderate" },
      { "id": "4", "name": "High" },
      { "id": "5", "name": "Very High" }
    ],
    "detection": [
      { "id": "1", "name": "Almost Certain" },
      { "id": "2", "name": "High" },
      { "id": "3", "name": "Moderate" },
      { "id": "4", "name": "Low" },
      { "id": "5", "name": "Undetectable" }
    ]
  },
  "enums": {
    "riskCategory": [
      { "id": "safety", "name": "Safety Risk" },
      { "id": "security", "name": "Security Risk" },
      { "id": "performance", "name": "Performance Risk" },
      { "id": "compliance", "name": "Compliance Risk" }
    ],
    "affectedSystems": [
      { "id": "braking", "name": "Braking System" },
      { "id": "steering", "name": "Steering System" },
      { "id": "powertrain", "name": "Powertrain" },
      { "id": "electrical", "name": "Electrical System" }
    ]
  },
  "cellDecorators": {
    "rpn": "function(info){ var val = info.value; $(info.cell).toggleClass('boldCol', true); $(info.cell).toggleClass('rpn1', val>0 && val<=150); $(info.cell).toggleClass('rpn2', val>150 && val<=350); $(info.cell).toggleClass('rpn3', val>350);}"
  },
  "styles": {
    ".rpn1": { "background-color": "#eaf5e9 !important", "color": "#1d5f20 !important" },
    ".rpn2": { "background-color": "#fff3d2 !important", "color": "#735602 !important" },
    ".rpn3": { "background-color": "#f8eae7 !important", "color": "#ab1c00 !important" },
    ".boldCol": { "font-weight": "600" }
  }
}

Column Type Reference — column definition properties and configuration
Enum Columns — enum and rating enumeration configuration
Multi-Enum Columns — multi-select enumeration setup
Calculated Columns — formula-based calculated columns
Date and Time Columns — temporal column configuration details
User Reference Columns — user assignment columns
OData API Endpoints — consuming data types via API
Field Mapping — Polarion field to Risksheet column binding
Supported Field Types — Polarion field type compatibility
Configuration Properties Index — full property reference

Sources

KB Articles

Support Tickets

#6102
#6028

Source Code

PolarionAppConfigManager.java
risksheet.json
ColumnTypeManager.java
AppConfigHelper.ts
GetSetUtil.java

​Data Type Summary

​Text Type

​Integer Type

​Float Type

​Boolean Type

​Date Type

​DateTime Type

​Time Type

​Currency Type

​Rating Type

​Duration Type

​Enum Type

​Multi-Enum Type

​Type Prefix Extraction and Colon Syntax

​User Reference Type

​Read-Only System Fields

​OData Type Mapping Reference

​Complete Example

​Related Pages

Data Type Summary

Text Type

Integer Type

Float Type

Boolean Type

Date Type

DateTime Type

Time Type

Currency Type

Rating Type

Duration Type

Enum Type

Multi-Enum Type

Type Prefix Extraction and Colon Syntax

User Reference Type

Read-Only System Fields

OData Type Mapping Reference

Complete Example

Related Pages