Skip to main content

​
Understand Baseline Loading States

Baseline loading in Nextedy RISKSHEET follows this progression: diagram When the baseline table shows ‘Loading’ indefinitely, this indicates a server-side error preventing data retrieval.
Support tickets confirm that a persistent ‘Loading’ state masks server-side errors rather than representing normal operation. The UI does not timeout or display error messages automatically—you must investigate server logs to identify the root cause.

​
Diagnose the Loading Issue

​
Step 1: Check Browser Console

Open browser developer tools (F12) and check the Console tab for errors:
  1. Press F12 to open developer tools
  2. Select the Console tab
  3. Look for failed AJAX requests or JavaScript errors
  4. Note any HTTP error codes (403, 500, etc.)

​
Step 2: Verify Baseline Selection

Ensure you’ve selected a valid baseline revision:
IssueVerification Step
No baseline selectedCheck dropdown shows specific revision, not “(none)“
Invalid revision IDVerify revision exists in Polarion document history
Wrong documentConfirm baseline belongs to current risk document

​
Step 3: Check User Permissions

Baseline loading requires read permissions for:
  • The current risk document
  • The baseline revision (historical version)
  • All linked work items referenced in the baseline
Try opening the baseline revision directly in Polarion document view. If you cannot access the revision there, you won’t be able to load it in Nextedy RISKSHEET either.

​
Resolve Server-Side Errors

​
Step 1: Collect Server Logs

Server logs contain the actual error details:
  1. Access Polarion Server: SSH or RDP into the Polarion server
  2. Locate Log Files: Navigate to <POLARION_HOME>/data/logs/
  3. Find Recent Entries: Check polarion.log for errors matching your baseline load timestamp
  4. Search for Keywords: Look for “risksheet”, “baseline”, “comparison”, or “OData” error messages

​
Step 2: Common Server Error Patterns

Error PatternLikely CauseResolution
NullPointerExceptionMissing baseline dataVerify baseline exists and contains work items
PermissionDeniedExceptionInsufficient access rightsGrant user read permissions to baseline revision
OutOfMemoryErrorLarge baseline datasetIncrease JVM heap size or reduce baseline scope
QueryTimeoutExceptionComplex query overheadOptimize query configuration or split risksheet

​
Step 3: Validate Configuration

Incorrect configuration can prevent baseline loading: 
{
  "gridProperties": {
    "comparingTo": "2024-01-15",
    "showUnchanged": true
  }
}
Verify:
  • comparingTo uses valid date format (YYYY-MM-DD) or revision ID
  • Baseline revision exists in document history
  • No syntax errors in risksheet.json
You can test baseline loading by adding ?comparingTo=<revision> to the RISKSHEET URL. This bypasses configuration and directly loads the specified baseline.

​
Handle Data Synchronization Delays

Baseline data loading can be slow for large datasets:

​
Expected Loading Times

Baseline SizeTypical Load Time
< 100 items1-3 seconds
100-500 items3-10 seconds
500-1000 items10-30 seconds
> 1000 items30+ seconds
If loading exceeds these thresholds, investigate:
  1. Network Latency: Check connection between client and Polarion server
  2. Server Load: Verify Polarion server CPU and memory usage
  3. Query Complexity: Review query configuration for expensive operations
  4. Linked Item Depth: Reduce number of linked item columns to improve performance

​
Optimize Baseline Loading Performance

​
Strategy 1: Reduce Column Count

Each linked item column requires additional queries: 
{
  "columns": [
    {"binding": "id", "header": "ID"},
    {"binding": "title", "header": "Title"},
    // Remove unnecessary linked item columns during comparison
    // {"type": "itemLink:requirement", "binding": "linkedReq"}
  ]
}

​
Strategy 2: Use Saved Views with Column Visibility

Create a dedicated saved view for baseline comparison with minimal columns:
  1. Open Nextedy RISKSHEET
  2. Hide unnecessary columns
  3. Save view as “Baseline Comparison”
  4. Load this view before activating baseline comparison
Some columns are marked as ‘not compared’ and display differently during baseline comparison. Focus on essential comparison columns (ID, title, status, risk parameters) for faster loading.

​
Verify Baseline Loading Works

  1. Select Baseline: Choose a baseline revision from the dropdown menu
  2. Observe Loading: The table should display ‘Loading…’ for 1-30 seconds
  3. Check Display: Baseline data should appear with color-coded change indicators:
    • Green rows: Items added since baseline
    • Red rows: Items removed since baseline
    • Yellow cells: Modified property values
  4. Test Filtering: Enable ‘Show Unchanged’ toggle to verify filtering works
  5. Verify Tooltips: Hover over changed cells to see before/after values
You should now see baseline comparison data loaded correctly. If loading still fails, contact Nextedy support with server log excerpts showing the specific error details.

​
See Also

Support TicketsSource Code
  • RisksheetProjectProperties.java
  • NewBaselineCommand.ts
  • ComparisonManager.ts
  • RisksheetViewServlet.java
  • RiskItemsODataCollectionView.ts