3775524 - Updating recruiting datetimeoffset format values via API but it only shows datetime format in results - Recruiting Management

When using API to update custom recruiting datetimeoffset fields, although using datetimeoffset format in request payloads, it is showing datetime format values in results.

SAP SuccessFactors Recruiting Management

1. Use API to update Recruiting entities including custom datetimeoffset fields.
2. In request payloads, input date format like "/Date(1704189306000+0000)/".
3. After updating, this field value is shown as date format "/Date(1704189306)/".

Although this custom field is defined as datetimeoffset field in OData dictionary, it is configured as only "date" type in recruiting templates. 

This is an expected system behavior.

If a field is configured as date type in recruiting, it only supports datetime values.

Recruiting Management, datetimeoffset, datetime, date, time, odata, API, upsert, jobapplication, jobrequisition, custom field, date type, odata dictionary, DateTime format, UTC, change, payloads, template, update , KBA , LOD-SF-RCM-API , Webservices & APIs , Problem