Select Export to Excel from the toolbar or context menu.
A progress notification appears with the message “Exporting to Excel — Please wait while the file is being generated.”
When the export completes, your browser downloads an .xlsx file named after the current document.
Unlike PDF export, Excel export does not require a clean/saved state. You can export at any time, including with unsaved changes in the grid. However, saving before export is recommended for consistency.
Risksheet handles each column type differently during export to ensure data integrity:
Risksheet App Excel Output
Boolean [x]
—>
“true”
Enum (dropdown)
—>
“High” (display name)
Multi-Enum [A][B][C]
—>
“Alpha, Beta, Gamma”
Item Link <a href=…>
—>
“REQ-1234” (plain text)
Multi-Link [{id,label}]
—>
“TASK-01\nTASK-02”
Server-Rendered <html>
—>
Plain text + linebreaks
Boolean fields export as the text values true or false rather than visual checkboxes.Enum fields export with their human-readable display names. For example, a severity field shows “High” rather than the internal ID.Multi-enum fields export as a comma-separated list of display names. Internal enum IDs are resolved to their configured name values from the enums section of risksheet.json. Unrecognized values are preserved as-is.Item link fields export as plain text showing the linked item label. HTML formatting from link references is stripped automatically.Multi-item link fields export as a newline-separated list of linked item labels. The JSON array of {id, label} objects is parsed, and each label is extracted as clean text. Items whose IDs begin with * are prefixed with an asterisk.Server-rendered fields export as plain text. List structures from HTML are preserved with line breaks between items.
Calculated columns (those using formulas in risksheet.json) display correctly in the grid but may appear empty in the Excel export for imported work items. This happens because formula values are only persisted to Polarion fields when a work item is edited within Risksheet.
Items imported into Polarion through bulk import or API will not have calculated column values in the Excel export until they are edited and saved in Risksheet. Version 24.5.1 introduced a data sync feature for formula columns that resolves this issue.
To ensure calculated columns export correctly:
Open the Risksheet document containing the imported items
Verify that calculated column values display correctly in the grid
If values are missing, save the document to trigger data sync (v24.5.1+)
Cell merging is the primary bottleneck for Excel exports. Large FMEA sheets with deep failure mode/cause/effect hierarchies can take a long time to process.
Switching to Flat table view before exporting can reduce export time from hours to minutes. The masterMergeOnly property controls whether the export uses hierarchical row merging or a flat table structure.
Additional performance settings:
Set refreshOnSave to false to avoid a full sheet reload before export, which also preserves your scroll position
Set moduleOnlyPermissions to true for faster loading on large sheets (v24.8.5+)
Version 25.2.0 includes optimizations specifically for merged cell processing during export
No custom Excel templates — Custom Excel export templates are not available. Use PDF export with custom scripts for advanced formatting needs.
Images not exported — Embedded images in work item fields do not appear in the Excel output.
Rich text stripped — Rich text formatting from Polarion fields is converted to plain text. Rich text can be displayed read-only in the grid using serverRender, but the formatting does not transfer to Excel.
