Troubleshooting FAQ

---

​

Loading and Display Issues

​

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 domain model referenced in sources does not exist, or there is a YAML syntax error in the configuration. Start by verifying the domain model exists in Administration > Nextedy POWERSHEET > Domain 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.

​

Why is my Powersheet stuck in read-only mode?

Read-only mode can be triggered by several conditions. Check the following causes in order: 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 domain model. Verify that the path (e.g., systemRequirements.systemRequirement.severity) follows a valid expansion path defined in your domain 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.

---

​

Configuration Issues

​

Why does my sheet configuration fail to load?

Configuration load failures are typically caused by YAML syntax errors, a reference to a non-existent domain model, or invalid property paths. The configuration editor in Administration > Nextedy POWERSHEET > Sheet Configurations provides validation that catches many issues at edit time. If the YAML file cannot be parsed at all, Powersheet falls back to its bundled default configuration, which usually appears as a generic empty sheet.

​

Why don’t my configuration changes take effect?

Powersheet loads its sheet configuration once when the widget initializes and does not hot-reload changes. After editing a YAML file through the administration interface, ensure the change was saved (committed to SVN) and then reload the Polarion document page in your browser. If you edited the domain model rather than the sheet configuration, both the model and every sheet referencing it need a page reload. For global-scope configurations, verify the change was saved to the _global project scope if that is where your sheet reads from.

​

Why does my entity picker show unexpected items?

Picker dropdowns are filtered based on pick constraints defined in the domain model for each entity type. If you see unexpected items, review the constraints.pick section on the relevant entity type — these entries control filtering by document.moduleFolder, document.moduleName, document.type, or document.component. The list.search property on the column definition controls which fields are searchable when typing in the picker. Missing or overly broad constraints are the most common cause of unfiltered picker results. For full constraint configuration details, see the Data Model Reference.

---

​

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 domainModelTypes section. Entity type names are case-sensitive and must match exactly — SystemRequirement is not the same as systemRequirement or Systemrequirement. Verify naming consistency between your domain model, sheet configuration column paths, and sources definitions. For a detailed walkthrough, see Fix Type Name Errors.

​

Why are my relationships not loading or navigating correctly?

Relationship navigation depends on three things being correctly aligned: the from and to entity types must exist in domainModelTypes, the linkRole must match a link role defined in the Polarion project, and the direct and back navigation property names must be referenced correctly in column binding paths and expand arrays. If any of these are mismatched, navigation paths will silently return no data. Review the Fix Relationship Errors guide for step-by-step diagnosis.

---

​

Administration and Setup Issues

​

How do I access the Powersheet administration interface?

Powersheet administration is integrated into Polarion’s standard administration area. Navigate to Administration > Nextedy POWERSHEET to find two sections: Domain Models for managing entity type and relationship definitions, and Sheet Configurations for column layout, views, formatters, and sources. Both sections use an embedded file manager that supports editing YAML files with project-scope and global-scope configurations. Global configurations (stored under the _global project) provide system-wide defaults that individual projects can override. See Administration Guides for detailed setup instructions.

​

Why do changes to my global configuration not appear in my project?

Global configurations provide defaults that can be overridden at project level. If a project has its own copy of a domain model or sheet configuration with the same name, the project-level file takes precedence over the global one. Check whether a project-level override exists in Administration > Nextedy POWERSHEET and either remove it to fall back to the global version, or update it to match your intended configuration.

---

​

Data and Save Issues

​

Why does saving data fail with validation errors?

Save failures typically occur when data violates constraints defined in the domain model or when required fields are empty. Common causes include: attempting to create a relationship that violates cardinality rules (e.g., adding a second link where cardinality is set to many-to-one), picking entities from outside the allowed moduleFolder or moduleName scope, or submitting duplicate property values where uniqueness is enforced. The error message usually includes a numbered list of failing conditions. For detailed resolution steps, see Resolve Validation Errors.

​

Why do dynamic value expressions return empty results?

Dynamic value expressions (using $context syntax like $context.source.document.component) resolve at runtime based on the current document context. If a dynamic expression returns an empty result, verify that the source document has the expected property set. For example, $context.source.document.component only works if the Polarion document has a component property assigned. Missing context values resolve to empty strings, which can cause picker constraints to match all items or no items depending on the filter logic. See Sheet Configuration Guides for more on dynamic values in source configurations.

---

​

Still stuck?

If your issue is not covered above, try the full Troubleshooting Guides for step-by-step walkthroughs, or browse the other FAQ pages:

• General FAQ — product overview and capabilities
• Configuration FAQ — sheet configuration questions
• Data Model FAQ — domain model and entity type questions
• Licensing FAQ — license and access questions

Sources

Support Tickets

• Powersheet configuration error guidance (incremental setup approach)

Source Code

• whole_rtm.template.yaml — complete RTM sheet configuration template
• powersheet.yaml — RTM column layout and sources configuration
• admin.cy.ts — administration interface tests
• Powersheet.tsx — main application component
• helpers.ts — dynamic value and expression evaluation