Understand Freeze Pane Options
Nextedy RISKSHEET provides freeze pane functionality similar to spreadsheet applications. You can lock:
- Header row: Keep column headers visible while scrolling vertically
- Left columns: Keep identifier columns (ID, Title) visible while scrolling horizontally
- Both: Freeze headers and left columns simultaneously
Set the number of left-side columns to freeze using the frozenColumns configuration property.
Edit your risksheet.json configuration:
{
"frozenColumns": 2,
"columns": [
{"name": "ID", "field": "id"},
{"name": "Title", "field": "title"},
{"name": "Severity", "field": "severity"},
{"name": "Occurrence", "field": "occurrence"}
]
}
With frozenColumns: 2, the first two columns (ID and Title) remain visible when scrolling horizontally to view Severity and Occurrence.
For FMEA/HARA workflows, freeze 1-3 leftmost columns containing work item identifiers (ID, Title, Risk Type). This lets users maintain context while reviewing risk parameters in right-side columns.
The header row is frozen by default. When you scroll vertically through hundreds of risk items, column headers remain visible at the top of the grid.
To adjust scroll performance for large datasets:
{
"virtualScrolling": true,
"pageSize": 100
}
virtualScrolling: Renders only visible rows (improves performance for 500+ items)
pageSize: Controls how many rows load at once (default: 100)
For wide risksheets with 20+ columns, configure scroll responsiveness:
{
"columnWidth": 150,
"autoResizeColumns": false
}
columnWidth: Default width in pixels for columns without explicit width settings
autoResizeColumns: When false, enables horizontal scrolling instead of shrinking all columns to fit viewport
Risksheets with 30+ visible columns can experience slower horizontal scrolling. Consider using saved views to create role-specific column sets (e.g., “Risk Assessment View” with 10 columns, “Full Details View” with all columns).
Test Freeze Pane Behavior
Test Horizontal Freezing
- Open a risksheet with
frozenColumns: 2 configured
- Scroll horizontally to the right using the bottom scrollbar
- Verify ID and Title columns remain visible on the left
- Continue scrolling to access columns beyond the viewport
- Open a risksheet with 100+ work items
- Scroll down through the list
- Verify column headers remain visible at the top
- Use ++page-down++ or mouse wheel to scroll quickly
| Scenario | Configuration | Result |
|---|
| Wide FMEA with 25 columns | frozenColumns: 3 | ID, Title, Risk Type stay visible |
| Deep hierarchy (500+ items) | virtualScrolling: true | Smooth vertical scrolling |
| Narrow viewport (laptop screen) | autoResizeColumns: false | Horizontal scrollbar appears |
| Review workflow (10 columns) | frozenColumns: 1 | Only ID frozen, more space for content |
Use ++ctrl+home++ to jump to the top-left cell and ++ctrl+end++ to jump to the bottom-right cell. Arrow keys navigate between cells while respecting frozen panes.
Adjust Frozen Column Count
To change the number of frozen columns without editing JSON:
- Open the Configuration Editor (if available in your RISKSHEET version)
- Navigate to Display Settings → Frozen Columns
- Set the desired number (typically 1-3)
- Click 💾 Save Configuration
- Refresh the widget to apply changes
Frozen columns not staying in place:
- Verify
frozenColumns value matches the number of columns you want to freeze
- Ensure the value is not greater than your total column count
- Clear browser cache and reload the page
Slow horizontal scrolling:
- Enable
virtualScrolling: true for large datasets
- Reduce visible column count using saved views
- Check browser console for JavaScript errors
Headers disappear when scrolling:
- This is expected behavior if header row freezing is disabled
- Check for custom CSS overrides that may affect header positioning
Verification
You should now see:
- Configured number of left columns remain visible when scrolling horizontally
- Column headers stay at the top when scrolling vertically through work items
- Smooth scrolling performance even with hundreds of rows
- Scrollbars appear only when content exceeds viewport dimensions
See Also