Skip to main content

​
Overview of Changes

The legacy format stored models in .polarion/models/ and configurations as LiveDoc attachments. The current format uses centralized administration through the Polarion UI with files stored in .polarion/nextedy/. diagram

​
Step 1: Move the Domain Model

Move the model YAML files from the legacy location to the new one:
  • Old path: .polarion/models/
  • New path: .polarion/nextedy/models/
Preferred: Use SVN (e.g., TortoiseSVN) to move the files, preserving history. Alternative: Open Administration > Nextedy POWERSHEET > Models, create a new model entry, and paste the YAML content from the old file.

​
Step 2: Define the Sheet Config Custom Field

In Administration > Documents & Pages > Document Custom Fields, create a new field:
PropertyValue
IdnextedySheetConfig
NameSheet Config
TypeEnum: Nextedy - Sheet Config
Decide whether the field applies to all document types or only specific ones (e.g., powersheet, userNeedsSpec).

​
Step 3: Create Sheet Configurations

  1. Open Administration > Nextedy POWERSHEET > Configurations
  2. Create new configuration entries
  3. Copy the YAML content from the old LiveDoc attachments that previously served as Powersheet templates
  4. Save each configuration
  5. Assign configurations to documents via the new nextedySheetConfig custom field

​
Step 4: Clean Up the Domain Model YAML

Remove the obsolete - name: syntax from entity type definitions. Run this regex search and replace: Search (regex): 
^(\s*)-\s*(name):\s*(\S+)(\s*)$
Replace: 
$1$3:$4
This converts entries from: 
- name: DesignRequirement
  polarionType: designOutput
To: 
DesignRequirement:
  polarionType: designOutput

​
Step 5: Clean Up the Sheet Configuration YAML

Remove the obsolete - binding: syntax from column definitions. Run this regex search and replace: Search (regex): 
^(\s*)-\s*(binding):\s*(\S+)(\s*)$
Replace: 
$1$3:$4
Then make these additional changes:
  • Remove the tool > sheet wrapper — move all nested content up to the root level
  • Remove - name: entries inside views configuration
  • Keep - name: in sources configuration for now (will be removed in a future version)
The - name: entries inside the sources section are still required in the current version. Only remove - name: from views and entity type definitions.

​
Step 6: Validate the Migration

  1. Open Administration > Nextedy POWERSHEET > Models and confirm the model loads without errors
  2. Open Administration > Nextedy POWERSHEET > Configurations and confirm sheet configurations are visible and parseable
  3. Open a LiveDoc linked to a new sheet configuration (via the custom field) and confirm the Powersheet table view displays correctly with data
You should now see the Powersheet view rendering with the same columns and data as before the migration, using the new configuration structure.

​
See Also

KB ArticlesSource Code
  • prod-powersheet-src/com.nextedy.powersheet.client/ltc-repo/__tests__/test-viewModel.ts
  • web.xml
  • PolarionQueryProcessor.java