- Upsert operation to SFAPI entity User fails with an error message as shown below:
<ns2:errorCode>INVALID_REQUEST_MESSAGE</ns2:errorCode><ns2:errorMessage>Invalid request message! Error: Invalid SFObject! Error: Invalid date value -- of field hiredate at [SFObject #19,field #16]!</ns2:errorMessage></ns2:SFWebServiceFault></detail>
Successfactors BizX System
From the SFAPI response, we see that error is due to the Invalid SFObject! Error: Invalid date value -- of field hiredate at [SFObject #19,field #16]!
This shows that the hiredate is invalid and the invalid SFObject is the 19th SFObject in the SOAP API request.
When you check SFAPI request, you see that the "Hiredate" is not maintained for SFObject #19 as shown below:
- Maintain the missing data for the Hire date field for 19th SFObject user.
Please make sure that all the required data is maintained in the Soap Request.This information can be found in SFAPI Data Dictionary once you expand the user entity.Here you can check which all are the required (mandatory) fields and they should be maintained.
KBA , LOD-SF-INT , SF Integrations - EC Payroll, Boomi/ HCI, API , Problem