Skip to main content

​
Identify the Error

Validation errors appear when saving changes in the sheet. The error dialog displays one or more numbered error messages describing what failed. Common symptoms include:
  • A save error dialog with numbered messages (e.g., “1. Error saving item…”)
  • Partial saves where some rows succeed but others fail
  • Entity dependency errors when creating linked work items
1

Understand the Save Process

Powersheet saves entities one by one in dependency order. Parent entities are saved before their children to ensure references are valid. This means:
  • Entity errors are collected across all items and reported as a single aggregated list after the save cycle completes
  • Application errors (server exceptions) interrupt the save immediately
  • Dependency sort failures (e.g., circular dependencies) prevent any saves from starting
diagram
2

Use Review Mode to Find Problems

Before saving, use review mode to identify items with validation problems. For how review mode tracks pending changes, see Working Sessions.
  1. Click the Review button in the toolbar (or use the review filter)
  2. Select the Problems filter to show only rows with validation errors
  3. Fix the highlighted issues before attempting to save
The review mode filters show four categories:
Always use the Problems review filter before saving large batches of changes. This lets you identify and fix validation issues proactively rather than discovering them through save error messages.
3

Common Validation Error Patterns

​
Missing Required Fields

If a required Polarion field is empty, the save will fail for that entity:
  • Check if mandatory custom fields have values
  • Verify that title is set for new work items
  • Ensure enum fields have valid values from the allowed list

​
Type Name Mismatches

The data model domainModelTypes keys must match exactly what the server expects. Errors referencing unknown types indicate a naming mismatch:
A common source of validation errors is using Polarion work item type IDs (e.g., requirement) in relationship from/to fields instead of data model entity type names (e.g., UserNeed). Always use the entity type name from domainModelTypes.

​
Constraint Violations

If constraints are configured on entity types (load, create, or pick constraints), saving may fail when data violates those constraints:
  • Document constraints: New items must be created in the specified document
  • Type constraints: Work items must match the expected document type
  • Component constraints: Items must belong to the correct component
4

Check Server Error Details

When the on-screen message is not enough, look in two places:
  • Browser DevTools (Network tab) — open your browser’s developer tools (F12), select Network, retry the save, and inspect the failing request’s response. Powersheet returns a structured error with a message field and an HTTP statusCode.
  • Polarion server log — server-side failures (HTTP 500) are recorded in the Polarion application log on the server. Ask your Polarion administrator for the log location if you do not have server access.
Error messages from the server include a human-readable message and an HTTP status code. Common codes:
5

Fix and Retry

After identifying the error source:
  1. Correct the data in the affected cells
  2. Use the Problems review filter to verify no remaining issues
  3. Save again
If multiple errors were reported, address them in dependency order — fix parent entity issues before child entities.

​
Verification

After resolving all validation errors:
  1. Click the Review button and select Problems — the list should be empty
  2. Save the changes
  3. You should now see a success notification with no error dialog
  4. Verify the saved data in Polarion to confirm persistence

​
See Also

Last modified on July 10, 2026