Risksheet Loading Issues

​

Diagnostic Steps

​

Solution 1: Validate Risksheet JSON Configuration

1. Navigate to your risksheet document in Polarion (e.g., Risks/HAZID)
2. Click Attachments tab
3. Download risksheet.json to your local machine
4. Validate JSON syntax using an online validator or command line:

# macOS/Linux validation
python3 -m json.tool risksheet.json > /dev/null && echo "Valid JSON" || echo "Invalid JSON"

5. Common JSON errors to fix:
   • Trailing commas in arrays or objects
   • Unescaped quotes in string values
   • Missing closing brackets } or ]
   • Duplicate property keys in same object

6. If validation fails, compare against a working template from RiskTemplates space
7. Re-upload the corrected risksheet.json file
8. Refresh the risksheet document page

​

Solution 2: Check Work Item Query Performance

1. Open the risksheet.json configuration
2. Locate the "query" property (usually near top of JSON)
3. Copy the Lucene query string (e.g., "type:failureMode AND module.id:Risks/HAZID")
4. Test query performance in Polarion’s Search interface
5. If search takes >10 seconds or returns >500 items, optimize:
   • Add module.id filter to limit scope: module.id:Risks/SFMEA
   • Use enum filters instead of text search: classification:(sc OR cc) instead of title:*safety*
   • Split large documents into separate modules by system element

​

Solution 3: Verify Column Configuration

1. Open risksheet.json and review columns[] array
2. For each column with "property" (custom field):
   Copy

   Ask AI

   {"id": "sev", "property": "fmeaSeverity", "title": "S"}
   
   Verify the custom field exists: Navigate to Administration → Work Items → Custom Fields and search for fmeaSeverity
3. For each column with "role" (link role):
   Copy

   Ask AI

   {"id": "rc", "dataType": "task", "role": "mitigates", "title": "Risk Control"}
   
   Verify the link role exists: Administration → Work Items → Link Roles and confirm mitigates is defined
4. Check field type compatibility:
   • Enum fields require "dataType": "string" and optional "pickerType": "enum"
   • Link columns require "dataType": "task" or "workItem" and "role": "linkRoleName"
   • Calculated columns use "formula": "JavaScript expression"
5. If field or role is missing, either:
   • Add it via Administration interface
   • Remove the column from risksheet.json
   • Replace with correct field/role name

​

Solution 4: Clear Browser Cache and Cookies

1. Chrome/Edge: Press Ctrl+Shift+Delete (Windows) or Cmd+Shift+Delete (Mac)
2. Select Time range: Last 7 days
3. Check Cached images and files and Cookies and site data
4. Click Clear data
5. Close all Polarion tabs
6. Reopen Polarion and navigate to risksheet document
7. Force refresh: Ctrl+F5 (Windows) or Cmd+Shift+R (Mac)

​

Solution 5: Check JavaScript Console for Errors

1. Open risksheet document that’s failing to load
2. Press F12 to open Developer Tools
3. Click Console tab
4. Look for red error messages
5. Common errors and fixes:

6. Screenshot the console output if error is unclear
7. Share with your Polarion administrator for advanced troubleshooting

​

Solution 6: Verify User Permissions

1. Navigate to the risksheet module (e.g., Risks/HAZID)
2. Check you can see work items in Document view (not risksheet)
3. If document is empty, you lack read permissions:
   • Contact project administrator
   • Request Read permission for the Risks space
   • Request membership in project role with work item access
4. Check risksheet widget permissions:
   • Navigate to Project → Properties → Permissions
   • Verify your role has Risksheet Widget access enabled

​

Verification

• Risksheet loads within 5 seconds
• Data grid displays with all configured columns
• Work items populate rows (no “Loading…” spinner stuck)
• Clicking cells allows inline editing (if permissions allow)
• Traffic lights indicator (if configured) shows colored status lights in top-right corner
• No red error messages in browser console

• Browser and version (Chrome 120, Firefox 115, etc.)
• Polarion version (check Help → About)
• Screenshot of browser console errors (F12 → Console tab)
• Copy of risksheet.json configuration (sanitize sensitive data)
• Lucene query from risksheet.json and result count from Search interface

​

See Also

• HARA Risksheet Configuration — Field mappings and ASIL formula
• System FMEA Risksheet Configuration — Multi-level FMEA structure
• Customize Risksheet Columns — Add custom fields and link roles
• Permission Denied Errors — Fix access control issues
• Formula Calculation Errors — Debug JavaScript formulas