This page covers general troubleshooting guidance based on Powersheet’s architecture. Exact error messages and behaviors may vary by version. Contact Nextedy support if issues persist.
Loading and Display Issues
Why does my Powersheet show a blank or empty sheet?
A blank sheet typically indicates one of three issues: the domain model referenced by your sheet configuration does not exist or has a syntax error, the data source query returns no matching work items, or the sheet is still loading data. Verify that themodel property in your sources section references an existing domain model and that the where clause matches work items in your project. Check that the Polarion document contains work items of the expected type.
Why is my Powersheet stuck in read-only mode?
Read-only mode can be triggered by several conditions:| Cause | Resolution |
|---|---|
| Invalid or expired license | Renew license via Administration > Nextedy POWERSHEET > License |
| User lacks write permissions | Contact your Polarion administrator to assign the appropriate role |
| Document opened at a historical revision | Navigate to the current (HEAD) revision of the document |
| Configuration explicitly sets read-only | Check the readOnly property in your sheet configuration |
Why are some columns not showing data?
Empty columns usually indicate a mismatch between the column binding path in the sheet configuration and the domain model. Verify that the binding path (e.g.,systemRequirements.systemRequirement.severity) matches a valid expansion path in your domain model and that the referenced properties exist on the target entity type. Also check that your data source expand section includes the navigation properties needed for the column paths.
Configuration Issues
Why does my sheet configuration fail to load?
Configuration load failures are typically caused by YAML syntax errors, references to a non-existent domain model, or invalid property names. The configuration editor provides JSON Schema validation that catches many issues at edit time. If the configuration file cannot be parsed, Powersheet falls back to the bundled default configuration.Why don’t my configuration changes take effect?
After editing a sheet configuration YAML file, you may need to reload the Powersheet document in your browser. Configuration changes are loaded once when the sheet initializes and do not hot-reload. If you edited the configuration through the Polarion administration interface, ensure the changes were saved (committed to SVN) before reloading.Why does my entity picker show unexpected items?
Picker dropdowns are filtered based on the constraints defined in your domain model and sheet configuration. If you see unexpected items, check thepick constraints on the relevant entity type — these control which entities appear in the picker. The list.search property defines which fields are searched when filtering in the picker dropdown.
Domain Model Issues
Why do I get errors about entity types not being found?
This error occurs when the sheet configuration references an entity type name that does not exist in the domain model. Entity type names are case-sensitive and must match exactly between the domain modeldomainModelTypes keys and the sheet configuration from and column binding paths. Double-check your naming and verify the domain model is loaded correctly.
How do I debug relationship expansion issues?
If related entities are not loading, verify three things: the relationship is defined in the domain modelrelationships array, the expand section in your data source includes the correct navigation property name, and the Polarion link role exists between the work items. Use the Model Helper tool to visualize the expansion paths in your domain model and confirm the structure is correct.
See Data Model FAQ for more on domain model relationships and entity type configuration.