Error Messages Reference

Verify in applicationError message text may vary between Risksheet versions. The messages listed here are representative. Always check the browser console (F12 > Console) for additional diagnostic details.

Configuration Errors

Errors that occur when loading or parsing the risksheet.json configuration file.

Error Message	Cause	Resolution
`No type attribute is defined for dataType`	A `dataTypes` entry (risk or task) is missing the required `type` property that specifies the Polarion work item type.	Add the `type` property to the affected `dataTypes` entry in `risksheet.json`. Example: `"risk": { "type": "failureMode", "role": "relates_to" }`
`For input string: <value>`	An enum value in the configuration does not match any valid enumeration option defined in Polarion. Commonly occurs when custom work item types use enum fields with values not properly mapped.	Verify that enum values in `risksheet.json` match the exact enum option IDs defined in Polarion’s custom field configuration XML. Check for typos and case sensitivity.

Configuration parse failuresIf risksheet.json contains invalid JSON syntax (missing commas, unquoted keys, trailing commas), the grid will fail to load entirely. Use a JSON validator to check syntax before uploading.

Save Operation Errors

Errors that occur when saving modified work items to the Polarion server.

Error Message	Cause	Resolution
`RISKSHEET rollbackTx`	A server-side transaction rollback occurred during the save operation. One or more work item updates failed, causing the entire batch to be rolled back.	Check the Polarion server log for the root cause. Common causes include workflow constraint violations, permission denials, or required field validation failures. See Save Operation Failures.
Save fails silently (no visible error)	The save operation completed on the client side but the server did not persist all changes. May occur when `refreshOnSave` is set to `false`.	Enable browser developer tools (F12) and check the Network tab for failed HTTP requests during save. Verify server logs for error details.

Session Errors

Errors related to session lifecycle and authentication.

Error Message	Cause	Resolution
Session timeout (HTTP 401/403 response)	The Polarion server session has expired due to inactivity. The session timeout is configured at the server level.	Reload the page to establish a new session. Unsaved changes will be lost. Save work frequently to minimize data loss risk. See Session Timeout Errors.

Preventing session timeoutsSave your work regularly. If you need to step away from a long editing session, save before leaving. The session timeout duration is controlled by your Polarion server administrator.

Rendering Errors

Errors that affect how cells, columns, or the grid itself are displayed.

Error Message	Cause	Resolution
Column displays blank or `[object Object]`	The column `type` does not match the actual Polarion field type, or the `bindings` references a field that does not exist on the work item.	Verify the `bindings` and `type` properties in the column configuration. Use exact Polarion field IDs. See Rendering and Display Errors.
Link column shows raw IDs instead of formatted links	The link rendering template or `cellRenderer` is missing or misconfigured for an `itemLink` or `multiItemLink` column.	Check that the column has a valid `cellRenderer` defined, or verify that the linked work item type and link role are correctly configured. See Link Rendering Issues.
Formula column shows `NaN` or `null`	The formula function references field bindings that do not exist on the current work item, or input values are empty/undefined.	Check the formula function for null/undefined handling. Add null checks: `var value = info.item['field']; return value ? value : null;`
Cell decorator throws JavaScript error	A `cellDecorators` function runs but fails — a syntax error, or a reference to an undefined property.	The error is reported in the browser console only. Open it (F12) to see the full JavaScript error, then fix the decorator function in the sheet configuration.
Risksheet configuration — `Column "<id>" refers to a cell decorator "<name>" that is not defined in the configuration.`	The column’s `cellRenderer` names an entry that the `cellDecorators` section does not contain, or the section is missing entirely. Usually a typo or a configuration copied without its decorators.	Add the named function to `cellDecorators`, or correct the `cellRenderer` value to match an existing entry. The cell renders without decoration until then; the rest of the sheet is unaffected.
Risksheet configuration — `The row header refers to a cell decorator "<name>" that is not defined in the configuration.`	`headers.rowHeader.renderer` names an entry that the `cellDecorators` section does not contain.	Add the named function to `cellDecorators`, or correct the `renderer` value.
Risksheet configuration — `Column "<id>" refers to a formula "<name>" that is not defined in the configuration.`	The column’s `formula` names an entry that the `formulas` section does not contain, or the section is missing entirely.	Add the named function to `formulas`, or correct the `formula` value. The column keeps its stored value until then, and every other column continues to render.

Two different failure modes, two different places to lookA missing formula or cell decorator — one the configuration never defines — is reported on the sheet itself (since v26.7.1), as a dismissible warning headed Risksheet configuration that names the column and the missing entry. It appears once per column and the sheet keeps working.A formula or decorator that is defined but throws while running is reported in the browser console only, with no on-sheet warning. If a value looks wrong and no warning appeared, open the console.

Permission Errors

Errors related to user permissions and access control.

Error Message	Cause	Resolution
Access denied when opening Risksheet	The user does not have read permission on the LiveDoc document or the work items within it.	Verify that the user has the required Polarion roles and permissions for the project and document. See Access Denied Errors.
Field is read-only unexpectedly	The column appears editable in configuration but is read-only at runtime. Certain system fields (`id`, `status`, `type`, `project`, `outlineNumber`, `author`, `resolution`, `created`, `updated`) are always read-only. Columns with `formula` or `serverRender` properties are also automatically read-only.	Check whether the field is a system field or has a `formula`/`serverRender` property. See Permission-Based Field Restrictions.

Work Item Operation Errors

Errors that occur when creating, deleting, or modifying work items through the grid.

Error Message	Cause	Resolution
`no rejected action found`	When deleting a risk item, the configured `rejectedAction` workflow action is not available on the work item’s current workflow state. Commonly occurs with imported work items that may be in a different workflow state than manually created items.	Verify that the workflow for the work item type includes the action specified in `dataTypes.risk.rejectedAction` (default: `reject`). Check that the action is available from the work item’s current state. See Risk Deletion Errors.
`Document NOT created`	The target document for new work items could not be created or accessed. May occur when the `createInDocument` path is invalid or the user lacks document creation permissions.	Verify the `createInDocument` path format (`folder/documentId`). Ensure the target folder exists and the user has document creation permissions. See Document Creation Errors.
Duplicate mitigation tasks created	Multiple task work items are created when only one was expected. May occur due to double-click on creation button or concurrent save operations.	Check for duplicate link relationships on the risk item. Remove extra tasks through the Polarion tracker. See Duplicate Mitigation Tasks.

Export Errors

Errors related to Excel and PDF export operations.

Error Message	Cause	Resolution
Calculated columns missing in export	Formula-based calculated columns may not appear in exported files if the export process does not evaluate client-side JavaScript formulas.	Verify export settings. Server-rendered columns (using `serverRender`) are generally included in exports. See Calculated Columns Missing in Exports.
PDF export fails or produces empty output	The PDF export Velocity template (`risksheetPdfExport.vm`) is missing or contains errors.	Verify that the PDF export template file exists and has valid Velocity syntax. See Export Performance Issues.

Query Errors

Errors related to data loading and query execution.

Error Message	Cause	Resolution
Query parsing error	The Lucene query syntax in a `query` (on `dataTypes.task`) or `queryFactory` configuration is invalid.	Check the query syntax against Polarion’s Lucene query format. Common issues include unescaped special characters and invalid field names. See Query Parsing Errors.
No items displayed in grid	The query returns no results. The document may be empty, the work item type filter may not match any items, or the document path may be incorrect.	Verify that the document contains work items of the configured type. Test the query in Polarion’s tracker search to confirm it returns expected results.

Date and Time Errors

Errors specific to date and time column operations.

Error Message	Cause	Resolution
Date column save error	Date values are sent in an unexpected format. The expected format is `yyyy-MM-dd` for date columns and ISO 8601 for datetime columns.	Verify the column `type` matches the Polarion field type (use `date` for date-only fields, `datetime` for timestamp fields). See Date Column Save Errors.

License Errors

Errors related to Risksheet licensing.

Error Message	Cause	Resolution
License validation error	The Risksheet license is expired, not installed, or the user is not assigned as an active user.	Contact your administrator to verify the license status. Ensure the current user is assigned in the active user list. See License Validation Errors.

Browser Console Diagnostic Steps

When encountering any error, the browser developer console provides the most detailed diagnostic information:

Open developer tools with F12 or Ctrl+Shift+I (Windows/Linux) / Cmd+Option+I (macOS).
Navigate to the Console tab to view JavaScript errors and warnings.
Navigate to the Network tab to inspect HTTP requests and responses during save operations.
Look for red error entries that include stack traces pointing to the error source.
Copy the error details when reporting issues to support.

Console filteringFilter console messages by typing risksheet or nextedy in the console filter box to isolate Risksheet-specific messages from other Polarion logs.

FAQ

Configuration Errors

Save Operation Errors

Session Errors

Rendering Errors

Permission Errors

Work Item Operation Errors

Export Errors

Query Errors

Date and Time Errors

License Errors

Browser Console Diagnostic Steps

See Also

​Configuration Errors

​Save Operation Errors

​Session Errors

​Rendering Errors

​Permission Errors

​Work Item Operation Errors

​Export Errors

​Query Errors

​Date and Time Errors

​License Errors

​Browser Console Diagnostic Steps

​See Also

Configuration Errors

Save Operation Errors

Session Errors

Rendering Errors

Permission Errors

Work Item Operation Errors

Export Errors

Query Errors

Date and Time Errors

License Errors

Browser Console Diagnostic Steps

See Also