Skip to main content

​
Before You Start

Risksheet and Powersheet share the same underlying architecture and domain model concepts. The migration primarily involves moving configuration files to new locations and updating document references. Your existing Polarion work items, link roles, and custom fields remain unchanged.
Create a copy of your project (or use a sandbox project) and perform the migration there first. Validate everything works before migrating your production project.

​
Step 1: Install Powersheet

Ensure Nextedy POWERSHEET is installed and licensed on your Siemens Polarion ALM server. See Installing Powersheet for details. After installation, verify that the Administration > Nextedy POWERSHEET menu section is available.

​
Step 2: Migrate the Domain Model

Risksheet domain models define entity types with workItems arrays and relationships. Powersheet uses the same YAML structure with an updated format.
  1. Locate your existing Risksheet model YAML (typically in .polarion/nextedy/models/ or .polarion/models/)
  2. If the model is in .polarion/models/, move it to .polarion/nextedy/models/ via SVN
  3. Open Administration > Nextedy POWERSHEET > Models and verify the model loads
The key domain model properties map directly:
Risksheet PropertyPowersheet EquivalentNotes
workItems[].namedomainModelTypes keysEntity type identifiers
workItems[].typepolarionTypePolarion work item type mapping
workItems[].propertiespropertiesEntity properties
relationships[].from / toRelationship definitionsSame syntax
relationships[].roleLink roleSame link role references
relationships[].cardinalityCardinalitySame cardinality values
If your model uses the legacy array-based entity format, convert it to the key-based format: Before (array-based): 
workItems:
  - name: Hazard
    type: hazard
    properties:
      - name: severity
        type: enum
After (key-based): 
domainModelTypes:
  Hazard:
    polarionType: hazard
    properties:
      severity:
        type: enum
The exact conversion syntax depends on your Risksheet version. Some versions may already use the key-based format. Open the model in Administration > Nextedy POWERSHEET > Models to verify it parses correctly.

​
Step 3: Create the Sheet Config Custom Field

If you do not already have the nextedySheetConfig custom field:
  1. Navigate to Administration > Documents & Pages > Document Custom Fields
  2. Create a new field:
    • Id: nextedySheetConfig
    • Name: Sheet Config
    • Type: Enum: Nextedy - Sheet Config

​
Step 4: Migrate Sheet Configurations

  1. Open Administration > Nextedy POWERSHEET > Configurations
  2. Create new configuration entries for each Risksheet view you want to preserve
  3. Copy the YAML content from your Risksheet configurations
  4. Adapt the column binding paths to use the Powersheet domain model entity names
A typical RTM sheet configuration in Powersheet: 
columnGroups:
  Risks:
    groupName: Risk Analysis
    groupStyle: orange

columns:
  title:
    title: Hazard
    width: 250
    hasFocus: true
  severity:
    title: Severity
    width: 100
  riskControls.riskControl.title:
    title: Risk Control
    width: 200
    columnGroup: Risks
    multiItem: true

sources:
  - id: hazards
    title: Hazards
    model: risk-model
    query:
      from: Hazard
    expand:
      - name: riskControls
        title: Risk Controls

​
Step 5: Bind Documents to Configurations

For each document that previously used a Risksheet view:
  1. Open the document properties
  2. Set the Sheet Config field to the appropriate Powersheet configuration
  3. Save the document
Ensure the domain model referenced by your sheet configuration defines all entity types and relationships used in column binding paths. Mismatched models cause columns to fail silently.

​
Step 6: Configure Powersheet Drive

Powersheet uses Powersheet Drive for sidebar navigation. Update the document query property if needed: 
com.powersheet.powersheetDocumentQuery=type:powersheet OR HAS_VALUE:templateDoc.KEY
This determines which documents appear in the Powersheet Drive sidebar topic.

​
Step 7: Validate the Migration

  1. Open Administration > Nextedy POWERSHEET > Models — confirm the domain model loads
  2. Open Administration > Nextedy POWERSHEET > Configurations — confirm sheet configurations are visible
  3. Open a migrated document — confirm the Powersheet table view displays correctly
  4. Create a test work item to verify save operations work
  5. Check that link roles and relationships resolve correctly in the sheet
You should now see the Powersheet table view rendering with your migrated data, columns, and relationships from the former Risksheet configuration.

​
See Also

KB ArticlesSupport TicketsSource Code
  • riskmanagement_model.yaml
  • prod-powersheet-src/com.nextedy.powersheet/src/META-INF/hivemodule.xml
  • prod-powersheet-src/com.nextedy.powersheet/src/com/nextedy/powersheet/PowersheetDocumentConfigurationService.java
  • prod-powersheet-src/com.nextedy.powersheet.client/src/modules/Powersheet/Powersheet.tsx
  • prod-powersheet-src/com.nextedy.powersheet.client/cypress/fixtures/configurations/whole_rtm.template.yaml