Skip to main content

Before You Start

Risksheet and Powersheet share the same underlying architecture and data 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.
1

Install Powersheet

Ensure 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.
2

Migrate the Data Model

Risksheet data 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 data model properties map directly:If your model uses the legacy array-based entity format, convert it to the key-based format:Before (array-based):
After (key-based):
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.
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
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 data model entity names
A typical RTM sheet configuration in Powersheet:
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 data model referenced by your sheet configuration defines all entity types and relationships used in column binding paths. Mismatched models cause columns to fail silently.
6

Configure Powersheet Drive

Powersheet uses Powersheet Drive for sidebar navigation. Update the document query property if needed:
This determines which documents appear in the Powersheet Drive sidebar topic.
7

Validate the Migration

  1. Open Administration > Nextedy Powersheet > Models — confirm the data 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

Last modified on July 10, 2026