KB-2409 Date field validation error persists after programmatically clearing invalid date value

Symptoms

1. User enters an invalid date value (e.g., 22/33/2026 or 22/55/8566) in a date field.
2. Appian displays validation error: The value [invalid date] is not a valid date. Valid format is dd/mm/yyyy.
3. Programmatic attempts to clear or update the field value using button actions with saveInto logic fail to remove the validation error.
4. The validation error persists on the UI until the user manually edits or clears the field.

Cause

This is the intended product design for a!dateField. The date field maintains an internal load variable that persists even when the value parameter changes. This internal load variable is only set to null when the value parameter is set to a valid date. Until value is a valid and non-null date, the internal load variable continues to be used, causing the validation error to persist.

Action

If you would like to be added to the Product Enhancement Request for this behavior, please raise a Support Case referencing the relevant existing product enhancement: #7020 - Date field should not display the validation message if the value is null.

This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support's policy to disclose how or when a product use case will be implemented.

Workaround

• Users must manually clear or correct the invalid date value in the field to remove the validation error.
• Alternatively, reload or refresh the page. Note that this will clear values in other fields unless a mechanism exists to temporarily save values before reloading.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2026