Question
EY
IN
Last activity: 3 Oct 2025 18:11 EDT
Incomplete DateTime error in Constellation
Configure a Date and Time field along with other components in a view and create a validate rule for checking null value for all the fields. When an incomplete date is entered (no month/year in the input date), it is suppressing other validation error. Is incomplete date triggering ootb client-side validation?
HCA Healthcare
US
Yes, Constellation runs browser-level (client-side) checks for Date/Time, so a partial date fires the OOTB client validation first and blocks your server-side Validate rule from showing its other messages. To fix the user experience, do one or more of these: disable free-text entry and force the calendar/picker so users can’t type a partial value; add an input mask so only complete dates are accepted; keep the field not-required at the control level and move your “null checks” to a single server-side Validate rule (so client-side doesn’t short-circuit); or add an edit-input/validate that normalizes partial input to blank on blur. Also review recent platform patches that adjusted Constellation client-side validation behavior and upgrade if you’re below 24.2.1/24.1.2. References: Support thread describing this symptom and Pega docs/patch notes on Date/Time and client validation.