> ## Documentation Index
> Fetch the complete documentation index at: https://learn.nextedy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Common Troubleshooting

> Quick answers to the most frequent issues encountered when working with Nextedy RISKSHEET.

<Tip title="How to use this page">
  Locate the symptom that matches what you see in your Risksheet document, read the short answer, then jump to the linked detailed page if you need configuration examples or root-cause explanations.
</Tip>

## Diagnostic Decision Path

<Frame>
  <img src="https://mintcdn.com/none-17b4493f/-Icoak49xQVOW38R/risksheet/diagrams/faq/troubleshooting-faq/diagram-1.svg?fit=max&auto=format&n=-Icoak49xQVOW38R&q=85&s=10cef050912a5052234774f865ef6f17" alt="diagram" style={{ maxWidth: "760px", width: "100%" }} width="760" height="320" data-path="risksheet/diagrams/faq/troubleshooting-faq/diagram-1.svg" />
</Frame>

## Configuration Issues

<AccordionGroup>
  <Accordion title="Why is my Risksheet grid showing no rows even though risk items exist in the document?">
    The most common cause is a mismatch between `dataTypes.risk.type` in the sheet configuration and the actual Polarion work item type used in your LiveDoc. Confirm the work item type ID matches exactly (case-sensitive), and verify that the document contains items of that type. See [Configuration Management](/risksheet/guides/configuration/index) for verification steps.
  </Accordion>

  <Accordion title="I edited my sheet configuration but the changes do not appear in the grid — what should I check?">
    The sheet configuration is attached to the document, but the page may still be showing a cached version. Reload the LiveDoc (full browser refresh, not just navigation) and confirm you edited the right configuration — the document configuration takes priority over the template configuration. See [Configuration Hierarchy](/risksheet/guides/configuration/index) for the inheritance rules.
  </Accordion>

  <Accordion title="Why do my formulas return undefined or NaN?">
    Formula errors most often come from referencing a property that does not exist on the row object. Use `info.item['columnId']` syntax with the exact column `id`, not the column header. Also confirm the column you are reading from has `bindings` set (plural — `bindings`, not `binding`) so values are actually loaded. See the [Formulas reference](/risksheet/reference/formulas/index) for parameter conventions and the `info` object structure.
  </Accordion>
</AccordionGroup>

## Column and Data Issues

<AccordionGroup>
  <Accordion title="Why does a column show empty cells even though the linked Polarion field has data?">
    This is almost always caused by an incorrect `bindings` value. The property is `bindings` (plural) and must contain the exact Polarion field ID — not the field label. Field IDs are case-sensitive. For linked-item bindings such as `task.title` or `harm.title`, the prefix must match the configured `dataTypes` key. See [Column Configuration](/risksheet/guides/columns/index).

    <Warning title="Common mistake">
      Writing `binding: severityRating` (singular) instead of `bindings: severityRating` (plural) silently produces empty columns — no error is thrown, the column just renders blank.
    </Warning>
  </Accordion>

  <Accordion title="How do I fix cell merging that does not work as expected?">
    Visual cell merging is controlled by the `levels` configuration. Each level must declare three properties: `name`, `controlColumn`, and `zoomColumn`. Columns merge when consecutive rows share the same value in the level's `controlColumn`. Also remember that the column `level` property is **1-indexed** — `level: 1` corresponds to `levels[0]`. See [Risk Management Guides](/risksheet/guides/risk-management/index).
  </Accordion>

  <Accordion title="Why are calculated columns (RPN, risk class) showing stale values?">
    Calculated columns rely on the formula being re-evaluated when source cells change. Confirm your formula returns a value (not undefined), reads from the right `info.item[...]` properties, and that the source columns have `bindings` configured. If the formula calls a function from the top panel template, also verify the top panel configuration loads correctly. See the [Formulas reference](/risksheet/reference/formulas/index).
  </Accordion>
</AccordionGroup>

## Styling and Conditional Formatting

<AccordionGroup>
  <Accordion title="Why are my cell colors not applying even though the cellDecorator runs?">
    A cellDecorator MUST use `toggleClass` to apply visual styling, because grid cells are reused across rows. The canonical form is jQuery `$(info.cell).toggleClass(...)`, as used in the product's reference templates (`wijmo.toggleClass(...)` is a non-canonical equivalent). Setting inline styles directly produces inconsistent results as cells scroll. Also confirm the CSS class name you toggle exists in the `styles` section, and that the style value is wrapped in `{}` braces, for example `'.rpn3': '{background-color: #e53935 !important;}'`. See [Styling and Formatting](/risksheet/guides/styling/index).

    <Note title="Style value format">
      Risksheet style values are CSS rules wrapped in braces. Forgetting the braces or omitting `!important` is a common reason styles silently fail to apply.
    </Note>
  </Accordion>
</AccordionGroup>

## Saving, Editing, and Permissions

<AccordionGroup>
  <Accordion title="Why can I open the Risksheet but not create new rows?">
    This usually indicates a PRO license. The Risksheet PRO license tier allows modifying existing rows but does not allow creating new rows — only the ALM, Requirements, or QA license tiers grant full create-and-modify access. The REVIEWER license is read-only. Verify the current user's assigned Polarion license. See [Licensing Questions](/risksheet/faq/licensing) and [Licensing Model](/risksheet/faq/licensing-model).
  </Accordion>

  <Accordion title="Why are some cells in my row read-only even though the column is editable?">
    This is typically intentional behavior driven by a cellDecorator. Risksheet supports per-row read-only logic by appending to `info.item.systemReadOnlyFields` inside a decorator function (a pipe-delimited string like `'|asilSeverity|asilExposure|'`). When a row is, for example, classified as "QM" in a HARA analysis, ASIL-specific fields become locked for that row only. Check your `cellDecorators` section for logic touching `systemReadOnlyFields`. See [Styling and Formatting](/risksheet/guides/styling/index).
  </Accordion>

  <Accordion title="Why does my new task item not appear after I create it from the grid?">
    If `dataTypes.task.canCreate: false` is set, task creation is globally disabled — users can only link to existing items. Similarly, individual itemLink columns can disable creation with `canCreate: false`. If creation is enabled but new items are not visible, confirm `dataTypes.task.createInCurrentDocument` or `dataTypes.task.createInDocument` (v24.8.1+) targets a document you have access to. See [Risk Management](/risksheet/guides/risk-management/index).
  </Accordion>
</AccordionGroup>

## Saved Views

<AccordionGroup>
  <Accordion title="My saved view is missing columns I expected — what should I check?">
    The view's `columnIds` array must use exact column `id` values (the property is `columnIds`, plural, not `columns`). You can use the special `@all` token to include all columns and the `-columnId` prefix to exclude one, for example `["@all", "-task"]`. To make a view load by default, set `defaultView: true` on the view object (v24.1.0+). See [Saved Views guide](/risksheet/guides/columns/index).
  </Accordion>
</AccordionGroup>

## Reviews and Approvals

<AccordionGroup>
  <Accordion title="Why does my approval review not change the Polarion document workflow status?">
    Risksheet's approval review creates approval-tagged comments but does NOT trigger Polarion's formal approval state transitions (draft → reviewed → approved). It is a review-tracking mechanism inside the grid. If you need full Polarion approval workflow integration, use Polarion's native document workflow alongside Risksheet's review feature. See [Review Management](/risksheet/guides/reviews/index).

    <Info title="Three review types">
      Risksheet supports comment-based, work-item-based, and approval-based reviews. Each has a different scope and traceability footprint.
    </Info>
  </Accordion>
</AccordionGroup>

## Reference Quick Table

| Symptom                                | Most likely cause                                           | Where to look                                                     |
| -------------------------------------- | ----------------------------------------------------------- | ----------------------------------------------------------------- |
| Empty grid                             | Wrong `dataTypes.risk.type`                                 | [Configuration Management](/risksheet/guides/configuration/index) |
| Empty column                           | `binding` (singular) instead of `bindings`                  | [Column Configuration](/risksheet/guides/columns/index)           |
| Stale formula                          | Source column missing `bindings`                            | [Formulas reference](/risksheet/reference/formulas/index)         |
| Wrong cell merging                     | `level` property is 1-indexed; check `controlColumn`        | [Risk Management Guides](/risksheet/guides/risk-management/index) |
| No cell coloring                       | Decorator not using `toggleClass`, or missing `{}` in style | [Styling and Formatting](/risksheet/guides/styling/index)         |
| Cannot create rows                     | PRO or REVIEWER license tier                                | [Licensing Model](/risksheet/faq/licensing-model)                 |
| Locked cells per row                   | `systemReadOnlyFields` in a cellDecorator                   | [Styling and Formatting](/risksheet/guides/styling/index)         |
| Missing columns in view                | `columnIds` typo or wrong column id                         | [Saved Views guide](/risksheet/guides/columns/index)              |
| Approval review has no workflow effect | By design — review-only, not workflow                       | [Review Management](/risksheet/guides/reviews/index)              |

## When to Escalate

<Tip title="Before contacting support">
  Capture the sheet configuration, the document ID, the Polarion version, the Risksheet plugin version, and a short description of the expected vs. actual behavior. Most configuration issues can be resolved by comparing your sheet configuration against the closest [solution template](/risksheet/reference/templates/index).
</Tip>

If a problem persists after checking the above, see the full [Troubleshooting](/risksheet/troubleshooting/index) section for deeper diagnostics, log locations, and recovery procedures. For configuration-related issues, the [Configuration Examples](/risksheet/reference/examples/index) page shows verified working snippets from production solution templates.