Loading and Display Issues - Nextedy Documentation

Why does my Powersheet show a blank or empty sheet?

A blank sheet typically means the data source query returned no matching work items, the data model referenced in sources does not exist, or there is a YAML syntax error in the configuration. Start by verifying the data model exists in Administration > Nextedy POWERSHEET > Data Models, then confirm work items of the expected polarionType exist in the project. Check the browser developer console for error messages that pinpoint the failure.

Start simpleWhen setting up a new sheet, begin with a minimal single-entity configuration and extend incrementally. Jumping straight to a complex multi-level RTM often leads to hard-to-diagnose errors.

Why is my Powersheet stuck in read-only mode?

Read-only mode can be triggered by several conditions. Check the following causes in order:

Cause	Resolution
Invalid or expired license	Renew via Administration > Nextedy POWERSHEET > License
User lacks write permissions	Ask your Polarion administrator to assign the appropriate role
Document opened at a historical revision	Navigate to the current (HEAD) revision
Column-level `isReadOnly` set to `true`	Remove or set `isReadOnly: false` on the affected column
Formatter applies a read-only style	Check the `formatters` section for rules that force read-only rendering
The sheet reports configuration issues in the bar above it	Fix the reported columns — see Fix Column Configuration Issues

A sheet made read-only by a configuration problem says so on the chip in the bar above it, and the panel behind it states that the sheet stays read-only until the problem is fixed. That is the one cause you do not have to work down this table to find.See Licensing FAQ for details on license-related access restrictions.

Why are some columns not showing data?

Empty columns usually indicate a mismatch between the column binding path in the sheet configuration and the data model. Verify that the path (e.g., systemRequirements.systemRequirement.severity) follows a valid expansion path defined in your data model relationships, that the referenced properties exist on the target entity type in domainModelTypes, and that your data source expand array includes the navigation properties the column path depends on. If the expansion path is missing from sources, the related data simply will not be loaded.