Skip to main content
Configuration load failures are typically caused by YAML syntax errors, a reference to a non-existent data 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, Nextedy Powersheet falls back to its bundled default configuration, which usually appears as a generic empty sheet.
Common YAML pitfallsIncorrect indentation, missing colons after keys, and unquoted special characters (such as * or &) are the most frequent causes of parse failures. Always use the built-in editor with schema validation to catch these errors before saving.
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 data 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.
A column whose configuration cannot be resolved is left out, and the rest of the sheet is built as usual — so the sheet opens, with fewer columns than the configuration asks for. Every omitted column is reported: a chip in the bar above the sheet counts the problems, and opening it names each column, why it could not be loaded, and what to change. The four problems recognised are a field that does not exist on the type, a path that cannot be followed, settings the column was rejected for, and two columns bound to the same field.Because a partly loaded sheet could otherwise be saved back without the missing columns, a configuration problem also makes the sheet read-only until it is fixed. Reading, sorting, filtering, searching and export stay available. Two columns on the same field are the exception — nothing is lost by dropping the second, so that one is reported without locking the sheet.For the walk-through, see Fix Column Configuration Issues; for what is detected and why, see Column Configuration Diagnostics.
Picker dropdowns are filtered based on pick constraints defined in the data 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.