3661977 - The datetime passed in API leading to unexpected result - OData API

You are using OData API, and would like to upsert a field with datetime/date type.

You calculate for the Unix timestamp, and provide the value in the API payload. (e.g. /Date(1759075200000)/ )

However, the API upsert leads to an unexpected date/datetime in SF instance (e.g. the start date has one day difference from the expected date).

SAP SuccessFactors HCM

• OData API

The datetime field in SF is based on UTC time zone, while the input datetime is calculated based on other time zone.

For example, /Date(1759075200000)/ is 2025-09-29 00:00 CST (or UTC+8).

It's equivalent to 2025-09-28 16:00 UTC, so date 2025-09-28 will be imported into SF.

Please make sure you are providing datetime value based on UTC time zone.

For example, if you would like to upsert Start Date "2025-09-29", please provide the value for "2025-09-29 00:00 UTC" (which is /Date(1759104000000)/).

date discrepancy, local time zone, date mismatch, time zone conversion, utc adjustment, insert, update , KBA , LOD-SF-INT-ODATA , OData API Framework , Problem