Skip to main content

​
Common Rendering Issues

Rendering errors typically manifest as missing data, incorrect formatting, or Java exceptions in server logs.
SymptomRoot Cause
Blank cells/columnsField type mismatch
NullPointerException in logsIncompatible document field type
Rich text formatting loss on editText field type limitation
UI inconsistent across nodesMulti-node cache sync issue
Enum not displayingEnum ID vs. name config mismatch

​
Field Rendering Exceptions in Logs

Java exceptions appearing in Polarion server logs during RISKSHEET rendering are often non-fatal and can be safely ignored. Common log patterns:
  • java.lang.ClassCastException when iterating document fields
  • NullPointerException during field conversion
  • UnsupportedOperationException for renderingLayouts field (fixed in 24.7.0+)
Diagnostic steps:
  1. Check RISKSHEET version - Versions 24.3.1+ provide detailed field identification in error messages
  2. Identify the problematic field - Error message shows which document field caused the exception
  3. Verify field type compatibility - Check if the field type is supported (see Supported Field Types)
  4. Test functional impact - If the RISKSHEET displays correctly despite log errors, the exception is non-fatal
Field rendering exceptions in logs are often harmless—the system automatically skips incompatible document fields during client rendering. Recent versions (24.3.1+) provide enhanced error messages to help identify which specific field causes the issue.
Version-specific issues:
VersionKnown IssueResolution
< 24.7.0UnsupportedOperationException for renderingLayouts fieldUpgrade to 24.7.0+
Polarion 23.10 upgradeField type incompatibilitiesUpgrade to RISKSHEET 24.7.2+ (complete fix)

​
Rich Text Formatting Loss

Editing rich text fields directly in RISKSHEET may cause line breaks and formatting to be lost. Workaround:
  1. Configure the column as read-only in risksheet.json to prevent inline editing:
{
  "columns": [
    {
      "id": "description",
      "binding": "description",
      "type": "text",
      "readOnly": true
    }
  ]
}
  1. Edit via Polarion’s native editor - Double-click the row header to open the work item lightbox, where rich text editing is fully supported
  2. Use plain text fields - For fields requiring frequent inline editing, use text or multi-line text column types instead of rich text
Nextedy RISKSHEET has incomplete support for editing rich text fields. Line breaks, formatting, and embedded content may be lost when editing rich text columns directly in the grid. This is a known product limitation. Use read-only columns or Polarion’s native editor for rich text content.

​
Enum Display Issues

Enum columns may display IDs instead of names, or show blank values. Check enum configuration:
  1. Verify enum ID vs. name setting - Most fields use enum IDs; status fields use enum names (see Enum Columns)
  2. Confirm enum values exist - Check that the enum option is defined in Polarion’s enumeration configuration
  3. Review filter configuration - Task-type and risk-type enums filter by configured types; ensure your enum belongs to the correct type
Configuration example (showing enum names): 
{
  "columns": [
    {
      "id": "priority",
      "binding": "priority",
      "type": "enum",
      "typeProperties": {
        "useNames": true
      }
    }
  ]
}

​
Multi-Node Cache Synchronization

In multi-node Polarion deployments, configuration changes may not propagate immediately, causing UI inconsistencies across nodes.
  1. Clear server cache - Restart all Polarion nodes or use Polarion’s cache invalidation API
  2. Check server logs - Open the configuration editor and check logs on each node for rendering differences
  3. Force configuration reload - Edit and save the configuration again to trigger synchronization
  4. Verify consistent deployment - Ensure the same RISKSHEET version is deployed to all nodes
When configuration appears correct on one node but incorrect on others, check server logs after opening the configuration editor. Log analysis is the primary troubleshooting step for diagnosing node-specific rendering issues.

​
Slow Page Load from Unresolvable Items

Repeated UnresolvableObjectException errors in GridItems API calls block page rendering.
  1. Check server logs - Look for repeated exceptions with work item IDs
  2. Verify work items exist - Confirm that referenced work items exist in Polarion
  3. Check project context - Ensure linked items are in the correct projects and visible to your user account
  4. Remove invalid references - Delete or update links pointing to missing or unreadable work items
UnresolvableObjectException errors are expensive—stack trace creation and error handling significantly slow page loads. Identify and remove references to missing work items to restore performance.

​
Verify Rendering is Correct

After resolving rendering issues, confirm display accuracy:
  1. Reload the RISKSHEET page (F5)
  2. Check that all expected columns display with correct data
  3. Verify enum values show expected options (IDs or names based on config)
  4. Test editing cells to ensure changes persist after save
  5. Review server logs to confirm no new exceptions appear

​
See Also

Support TicketsSource Code
  • AppConfig.ts
  • ExportToExcel.ts
  • MultiItemLinkEditor.ts
  • NewBaselineCommand.ts
  • SheetConstants.ts