Error Message Summary
| Category | Errors | Warnings | Info |
|---|---|---|---|
| Configuration parsing | 8 | 1 | 3 |
| Data operations (save/create/delete) | 15 | 2 | 0 |
| Field handling (enum/date/text) | 11 | 1 | 0 |
| Link and traceability | 6 | 1 | 0 |
| PDF export | 1 | 0 | 1 |
| Permission and access | 5 | 0 | 0 |
| UI and client-side | 8 | 4 | 7 |
Configuration Errors
These errors occur when RISKSHEET loads or parses yourrisksheet.json configuration.
”Error while reading configuration”
Source:PolarionAppConfigManager.get()
Severity: Error
The risksheet.json file cannot be read from the document or template.
Causes:
- The file is not attached to the document or its template
- The file is corrupted or contains invalid JSON
- The document is not accessible (permissions issue)
- Open the document in Polarion and verify
risksheet.jsonis attached - Validate the JSON syntax (check for missing commas, unmatched brackets)
- Try the Configuration Editor: Menu > Configure
”Cannot parse config”
Source:PolarionAppConfigManager.parse()
Severity: Error
The JSON is syntactically valid but contains structural errors.
Solution: Compare your configuration against a working template. Check that columns is an array, dataTypes is an object, and all required fields are present.
”Invalid configuration”
Source: Client-sideAppConfigParser
Severity: Info (logged to console)
The client received configuration that doesn’t match expected structure.
Solution: Open browser developer tools (F12) and check the console for details about which property is invalid.
”Invalid column config, itemLink bindings without dot.”
Source:RisksheetPolarionServiceImpl.toRiskItem()
Severity: Warning
An itemLink or multiItemLink column has a bindings value without dot notation (e.g., "title" instead of "task.title").
Solution: Update the column’s bindings to use dot notation: "task.fieldName" where task matches the column’s id.
Permission and Access Errors
”You do not have permissions to create new items.”
Source:RisksheetPolarionServiceImpl.create()
Severity: Error
The current user lacks create permission for the target work item type or document.
Solution:
- Verify user has the “Create Work Items” permission in the Polarion project
- Check document-level permissions aren’t restricting access
- Contact your Polarion administrator to grant appropriate roles
”document not accessible”
Source:RisksheetPolarionServiceImpl (multiple methods)
Severity: Error
The Polarion document referenced in the operation cannot be accessed.
Causes:
- The document was deleted or moved
- The user lacks read permission for the document
- The
createInDocumentpath indataTypes.taskpoints to a non-existent document
- Verify the document exists at the expected path
- Check user permissions on the document
- If creating tasks in a separate document, verify
dataTypes.task.createInDocumentis correct
”Work item not accessible”
Source:RisksheetPolarionServiceImpl.update() / .run()
Severity: Error
A specific work item cannot be read or modified.
Solution: The work item may have been deleted by another user, or permissions changed. Refresh the page and try again.
”cannot check permission”
Source:PolarionAppConfigManager.checkConfig()
Severity: Error (logged)
Permission validation failed during configuration check.
Solution: This is usually transient. Refresh the page. If persistent, check that the Polarion server is responsive and your session hasn’t expired.
Data Operation Errors
”cannot save field for type”
Source:GetSetUtil.setValue()
Severity: Error
A field value cannot be written to the Polarion work item, typically due to type mismatch.
Solution:
- Check that the column
typematches the Polarion field type - Verify the value being saved is valid for the field (e.g., valid enum option, parseable date)
- See Date Column Save Errors for date-specific issues
”cannot save enum”
Source:GetSetUtil.setEnum() / .setMultiEnum()
Severity: Error
An enum value doesn’t match any option in the Polarion enum definition.
Solution:
- Verify the enum option ID exists in Polarion’s enum configuration
- Check for case sensitivity — enum IDs are case-sensitive
- If using dependent enums, ensure parent enum value is set first
”cannot parse date”
Source:GetSetUtil.parseDate() / .parseDateOnly() / .parseTimeOnly()
Severity: Error
A date/time value cannot be parsed from the input string.
Solution: Ensure dates use ISO 8601 format (YYYY-MM-DD). Check your locale settings if date parsing fails consistently.
”cannot save text”
Source:GetSetUtil.setText() / .setString()
Severity: Error
A text field value cannot be saved, usually due to field length limits or encoding issues.
Solution: Check that the text doesn’t exceed the Polarion field’s maximum length. Avoid special characters that may cause encoding problems.
”RISKSHEET rollbackTx”
Source:RisksheetPolarionServiceImpl.rollbackTransaction()
Severity: Error (logged)
A save transaction was rolled back. Your changes were NOT persisted.
Solution: This typically means one or more work item updates in the batch failed validation. Check other error messages in the server log for the specific cause. Try saving again with fewer changes.
Link and Traceability Errors
“‘FROM’ work item type unknown” / “‘TO’ work item type unknown”
Source:RisksheetPolarionServiceImpl.getValidLinkRole()
Severity: Error
The configured link role references work item types that don’t exist in the project.
Solution:
- Verify
dataTypes.task.typematches an existing Polarion work item type - Verify
dataTypes.risk.typematches an existing type - Check that the link role is defined between these two types in Polarion
”This item is already linked to selected row.”
Source: Client-sideSaveCellInterceptor
Severity: Warning (alert)
You attempted to link a work item that is already linked to the current risk item.
Solution: No action needed — the link already exists. Choose a different work item or cancel the operation.
”Please select or enter a valid work item.”
Source: Client-sideSaveCellInterceptor
Severity: Warning (alert)
The autocomplete field value doesn’t match any existing work item.
Solution: Use the autocomplete dropdown to select an existing work item, or create a new one using the ”+” button.
Client-Side Warnings
”There are unsaved changes. Please save the document first.”
Source: Multiple command handlers Severity: Warning (alert) You attempted an operation (comparison, baseline, formula recalculation) that requires a clean state. Solution: Click Save before performing the operation.”Overwrite not supported with Refresh On Save = false”
Source: Context menu handler Severity: Warning (alert) The overwrite operation requiresglobal.refreshOnSave: true in the configuration.
Solution: Enable refresh on save in your configuration, or perform the operation differently.
”You have read-only access only. (Reviewer License)”
Source:ReviewerCommand
Severity: Warning (alert)
Your license type only permits viewing, not editing.
Solution: Contact your administrator to upgrade your license tier. See License Tiers.
”No language module for [culture], falling back to en”
Source: Client-side initialization Severity: Warning (console) The configured locale isn’t available. RISKSHEET falls back to English. Solution: Check yourglobal.culture setting against supported culture codes.
Related Pages
- Save Operation Failures — Detailed save troubleshooting
- Rendering and Display Errors — Visual rendering issues
- Configuration Validation Rules — Property validation details
- Session Timeout Errors — Session-related issues