3742331 - EmpJob upsert returns 200 but position not updated due to mismatched startdate

• An EmpJob upsert to OData v2 returns HTTP 200 with editStatus “UPSERTED”, but the position value does not update and remains empty in new hire data.
• The upsert response shows status OK without an error message.

SAP SuccessFactors Onboarding

Timestamp of startDate mismatched.

In below Example:

POST <api url>/odata/v2/upsert

{
    "__metadata": {
        "uri": "EmpJob(startDate=datetime'2026-06-01T00:00:00',userId='XXX')",
        "type": "SFOData.EmpJob"
    },
    "seqNumber": "1",
    "eventReason": "HIRNEW",
    "startDate": "/Date(1775001600000)/",
    "company": "XX",
    "timezone": "EST",
    "managerId": "XXXX",
    "position": "XXXX",
    "userId": "XXXX"
}

1775001600000 is actually 2026-04-01T00:00:00, which mismatch startDate=datetime'2026-06-01T00:00:00'.

Ensure the timestamp of startDate is correct.

empjob, upsert, 200 ok, editstatus upserted, position not updated, onboarding, odata v2, startdate, datetime mismatch, new hire data, job information, timestamp alignment, , KBA , LOD-SF-OBX-ATS , ATS Integration , Problem