@Rajak9999 We cannot know why the user entered a seemingly non-existent date 19000000. While it appears to be attempting to represent a date (possibly in YYYYMMDD format), it's not properly formatted according to Pega's date parsing rules.

Hopefully the below will help you to fix this when dealing with Service-REST.

⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.

Supported Date Formats in Pega Service-REST Pega supports several ISO 8601 standard formats for date/time values. Here are the main supported formats:

1. Date-only formats:
   • yyyy-MM-dd (e.g., 2025-01-24)
   • yyyyMMdd (e.g., 20250124)
2. Date-time formats:
   • yyyy-MM-ddThh:mm:ss.ffffff (e.g., 2025-01-24T15:30:00.000)
   • yyyyMMddThhmmssZ (e.g., 20250124T153000Z)
   • yyyy-MM-ddThh:mm:ss.nnnnnn+|-hh:mm (with timezone offset)

How to Fix This Issue To resolve this issue in Service-REST, you have several options:

1. Format Standardization
   • Ensure the incoming date value is properly formatted according to one of the supported formats
   • For your case, if '19000000' is meant to represent January 1, 1900, it should be formatted as either:
     • '1900-01-01' (ISO format)
     • '19000101' (compact format)
2. Implementation Approaches
   • Add a data transform to convert the incoming format to a Pega-compatible format
   • Use appropriate parameter property types in your Service-REST
   • Implement proper validation rules to catch and handle invalid date formats before they reach the data transform
3. Best Practices
   • Use the ISO 8601 format (yyyy-MM-dd) for date-only values
   • Include proper error handling for date parsing
   • Consider adding input validation at the service layer
   • Document the expected date format in your service specifications

REFERENCS

Loading Data Types Documentation

Date Properties Guide

Parsing Date Values Documentation