> ## Documentation Index
> Fetch the complete documentation index at: https://learn.nextedy.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Resolve Validation Errors
> Diagnose and fix Nextedy POWERSHEET save operation errors caused by data validation failures, constraint violations, and entity dependency issues in Siemens Polarion ALM.
export const LastReviewed = ({date}) => {
if (!date) return null;
const formatted = new Date(`${date}T00:00:00Z`).toLocaleDateString("en-US", {
year: "numeric",
month: "long",
day: "numeric",
timeZone: "UTC"
});
return
Last reviewed on {formatted}
;
};
## 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
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
Before saving, use review mode to identify items with validation problems. For how review mode tracks pending changes, see [Working Sessions](/powersheet/concepts/working-sessions#the-change-buffer).
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:
| 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 |
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.
### 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:
```yaml theme={null}
domainModelTypes:
UserNeed: # This exact name is used in queries
polarionType: requirement # This maps to the Polarion type
```
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
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:
| 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) |
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
* [Handle Validation Errors](/powersheet/guides/save-operations/handle-validation-errors) -- validation handling in save operations
* [Create a Work Item](/powersheet/guides/save-operations/create-work-item) -- creating items with required fields
* [Fix Type Name Errors](/powersheet/guides/troubleshooting/fix-type-name-errors) -- type naming issues
* [Fix Relationship Errors](/powersheet/guides/troubleshooting/fix-relationship-errors) -- relationship configuration errors
***