> ## 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.

# Date Column Save Errors

> Resolve save failures and formatting issues specific to date, datetime, and time columns in Nextedy RISKSHEET.

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 <p className="mt-10 text-sm text-gray-400 dark:text-zinc-500 not-prose">
      Last reviewed on {formatted}
    </p>;
};

## Symptoms

* Save fails after editing a date cell with a `format` property configured
* Date values revert to unexpected formats after saving
* Upstream date columns cannot be edited despite configuration changes
* Custom Polarion scripts interfere with date field saves on certain rows

## Fix: "format" Property Causing Save Failures (v24.5.0)

In Risksheet version 24.5.0, adding a `format` property to date-only columns caused save failures due to a timezone fix regression.

**Before (causes save error in v24.5.0):**

```yaml theme={null}
id: dueDate
header: Due Date
bindings: dueDate
type: date
format: dd/MM/yyyy
```

**After (workaround -- remove format property):**

```yaml theme={null}
id: dueDate
header: Due Date
bindings: dueDate
type: date
```

<Warning title="Version 24.5.0 date format regression">
  Adding a `format` property to date-only columns causes save failures in Risksheet version 24.5.0. The workaround is to remove the `format` property and enter dates in `YYYY-MM-DD` format directly in the cell. This issue has been addressed in subsequent versions.
</Warning>

## Date Column Types

Risksheet supports three temporal column types, each with different storage and display behavior:

| Column Type | Format        | Storage        | Example               |
| ----------- | ------------- | -------------- | --------------------- |
| `date`      | Date only     | `yyyy-MM-dd`   | `2024-06-15`          |
| `datetime`  | Date and time | Full timestamp | `2024-06-15T14:30:00` |
| `time`      | Time only     | `hh:mm:ss`     | `14:30:00`            |

The system automatically converts between Polarion date types and the display format. Date columns parse `YYYY-MM-DD` format to a local time Date object before applying the column format for display.

<Frame>
  <img src="https://mintcdn.com/none-17b4493f/t34k0QhMnn4JCqkc/risksheet/diagrams/troubleshooting/date-column-save-errors/diagram-1.svg?fit=max&auto=format&n=t34k0QhMnn4JCqkc&q=85&s=19b31090da1a5c85bdbaad2d102088ea" alt="diagram" style={{ maxWidth: "600px", width: "100%" }} width="600" height="160" data-path="risksheet/diagrams/troubleshooting/date-column-save-errors/diagram-1.svg" />
</Frame>

<Tip title="Date entry without format property">
  When the `format` property is removed as a workaround, enter dates in `YYYY-MM-DD` format directly in the cell (e.g., `2024-06-15`). The system handles the conversion automatically.
</Tip>

## Fix: readOnly Property Is Case-Sensitive

If you cannot edit an upstream date column despite setting it to editable, check the capitalization of the `readOnly` property.

**Incorrect (will not work):**

```yaml theme={null}
id: upstreamDate
bindings: upstreamDate
readonly: false
```

**Correct:**

```yaml theme={null}
id: upstreamDate
bindings: upstreamDate
readOnly: false
```

<Warning title="Case-sensitive property name">
  The `readOnly` property must use camelCase with an uppercase `O`. Using `readonly` (all lowercase) has no effect. This is a very common configuration mistake when making upstream columns editable.
</Warning>

## Fix: Custom Script Interference

Custom Polarion scripts that validate work item fields (such as duplicate title checks) can interfere with Risksheet save operations, causing inconsistent save behavior across rows.

If some date fields save correctly but others fail:

1. Check Polarion server logs for custom script errors during save
2. Identify which workflow scripts run on the affected work item type
3. Test saving with custom scripts temporarily disabled to confirm the cause

<Info title="Verify in application">
  The interaction between custom Polarion workflow scripts and Risksheet save operations depends on your specific project configuration. Review your workflow scripts for field validation logic that may reject date changes.
</Info>

## System Read-Only Fields

Certain fields cannot be edited through Risksheet regardless of configuration. The following are always read-only: `id`, `status`, `type`, `project`, and `outlineNumber`. Additionally, system fields like `author`, `resolution`, `created`, `updated`, and `type` are automatically set to read-only. Date columns bound to these fields will not accept edits.

## Verification

After applying the resolution:

1. Open the Risksheet document with date columns
2. Edit a date cell and enter a value in `YYYY-MM-DD` format
3. Save the document and confirm the save completes without errors
4. Verify the date value persists correctly after page refresh

You should now see date columns saving successfully with correct values displayed in the grid.

## See Also

* [Save Operation Failures](/risksheet/troubleshooting/save-failures) -- general save troubleshooting
* [Cell Editing Issues](/risksheet/troubleshooting/cell-editing-issues) -- other editing problems
* [Calculated Columns Missing in Exports](/risksheet/troubleshooting/calculated-columns-export) -- formula persistence issues

<LastReviewed date="2026-06-24" />