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
Step 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
Step 2: Use Review Mode to Find Problems
Before saving, use review mode to identify items with validation problems:- Click the Review button in the toolbar (or use the review filter)
- Select the Problems filter to show only rows with validation errors
- Fix the highlighted issues before attempting to save
| Filter | Description |
|---|---|
| Added | Newly created items not yet saved |
| Modified | Items changed since last save |
| Deleted | Items marked for deletion |
| Problems | Items with validation errors |
Step 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
titleis set for new work items - Ensure enum fields have valid values from the allowed list
Type Name Mismatches
The domain modeldomainModelTypes keys must match exactly what the server expects. Errors referencing unknown types indicate a naming mismatch:
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
Step 4: Check Server Error Details
Error messages from the server include a human-readable message and an HTTP status code. Common codes:| Status Code | Meaning | Typical Cause |
|---|---|---|
| 400 | Bad Request | Invalid data format or missing required field |
| 403 | Forbidden | Insufficient permissions to modify the item |
| 404 | Not Found | Referenced entity does not exist |
| 409 | Conflict | Concurrent modification by another user |
| 500 | Server Error | Internal server issue (check server logs) |
Step 5: Fix and Retry
After identifying the error source:- Correct the data in the affected cells
- Use the Problems review filter to verify no remaining issues
- Save again
Verification
After resolving all validation errors:- Click the Review button and select Problems — the list should be empty
- Save the changes
- You should now see a success notification with no error dialog
- Verify the saved data in Polarion to confirm persistence
See Also
- Handle Validation Errors — validation handling in save operations
- Create a Work Item — creating items with required fields
- Fix Type Name Errors — type naming issues
- Fix Relationship Errors — relationship configuration errors
Sources: test-saveManager.ts, filter-items-for-review.ts, ConfigProvider.tsx, HttpErrorInfo.java, ticket insights
Sources
Sources
Support TicketsSource Code
prod-powersheet-src/com.nextedy.powersheet.client/ltc-repo/packages/sheet/commands/filter-items-for-review.tsprod-powersheet-src/com.nextedy.powersheet.client/src/modules/ConfigProvider/types/UserPermissions.d.tsprod-powersheet-src/com.nextedy.powersheet.client/src/modules/ConfigProvider/ConfigProvider.tsxHttpErrorInfo.javaprod-powersheet-src/com.nextedy.powersheet.client/ltc-repo/__tests__/test-saveManager.ts