Skip to main content

​
Prerequisites

  • At least one sheet configuration created in Administration > Nextedy POWERSHEET > Configurations
  • A domain model configured in Administration > Nextedy POWERSHEET > Models
  • The nextedySheetConfig custom field defined for your document type

​
Step 1: Create the Custom Field

If the nextedySheetConfig custom field does not yet exist, create it in Siemens Polarion ALM:
  1. Navigate to Administration > Documents & Pages > Document Custom Fields
  2. Decide whether the field applies to all documents or only a specific document type (e.g., powersheet, userNeedsSpec)
  3. Create a new field with these settings:
PropertyValue
IdnextedySheetConfig
NameSheet Config
TypeEnum: Nextedy - Sheet Config
The enum provider automatically discovers configuration files from both global and project-specific repository locations. Global configurations appear with a (Global) suffix in the dropdown. There is no default configuration — users must explicitly select one.

​
Step 2: Assign the Configuration to a Document

  1. Open the Polarion LiveDoc you want to connect to Powersheet
  2. Open the document properties panel
  3. In the Sheet Config field, select the desired sheet configuration from the dropdown
diagram The dropdown lists all available configurations:
  • Project-specific configurations — shown by filename without path
  • Global configurations — shown with (Global) suffix, ID starts with /

​
Step 3: Understand Configuration Scopes

Powersheet discovers configurations at two levels:
ScopeRepository LocationID FormatUse Case
Project.polarion/nextedy/sheet-configurations/Filename onlyProject-specific layouts
GlobalGlobal repository locationStarts with /Shared across multiple projects
A single sheet configuration can be reused across multiple documents. Each document references the configuration independently through its nextedySheetConfig field.
The sheet configuration references column binding paths that must exist in the associated domain model. If you assign a configuration designed for one domain model to a document using a different model, columns with unresolvable bindings will fail to display correctly.
New users should begin with a minimal single-entity configuration and extend incrementally. Jumping directly to complex multi-entity configurations leads to hard-to-diagnose errors. See Incremental Configuration Approach for guidance.

​
Step 4: Use Template-Based Documents

For standardized deployments, you can create template documents that already have the sheet configuration pre-assigned. New documents duplicated from the template inherit the configuration assignment, saving administrators from manually assigning configurations for each new document. Templates can be duplicated across projects. The configuration and domain model are resolved in the target project context.

​
Verification

After assigning the configuration and saving the document:
  1. Open the LiveDoc in Polarion
  2. You should now see the Powersheet table view embedded in the document, displaying columns and data according to your configuration
  3. The sheet should load data from the sources defined in the configuration
  4. The Powersheet Drive sidebar topic should list your document

​
See Also

KB ArticlesSupport TicketsSource Code
  • prod-powersheet-src/com.nextedy.powersheet/src/com/nextedy/powersheet/PowersheetService.java
  • prod-powersheet-src/com.nextedy.powersheet.client/ltc-repo/cypress/e2e/Admin/create-document-connection-and-change-status.spec.ts
  • prod-powersheet-src/com.nextedy.powersheet/src/com/nextedy/powersheet/enumProvider/SheetConfigEnumProvider.java
  • prod-powersheet-src/com.nextedy.powersheet.client/cypress/e2e/userFlows/multiple-entity-type-flow.cy.ts
  • prod-powersheet-src/com.nextedy.powersheet/src/META-INF/hivemodule.xml