3713701 - OData API Error "Field deleted is not valid for template with the index 0, JobRequisition:Field deleted is not valid for template with the index 0" - Recruiting Management

An error occurs when attempting to create job requisitions via Integration Center or OData API: "Field deleted is not valid for template with the index 0, JobRequisition:Field deleted is not valid for template with the index 0"

SAP SuccessFactors Recruiting Management

1. Attempt to create job requisitions via Integration Center.
2. Populate the field deleted with various values (e.g., Not Deleted, 0 or false).
3. Observe the error message: "Field deleted is not valid for template with the index 0, JobRequisition:Field deleted is not valid for template with the index 0".

The property "deleted" is neither supported nor required for creating or updating a 'Not Deleted' job requisition.

It is only supported when deleting a job requisition, in which case it will be set to deleted=true.

Remove the field association from "deleted" when creating or updating job requisitions through OData API.

For Updating Job Requisitions:

• Set isDraft=true as recommended in the KBA 2771951 to bypass the mandatory value mapping.

For Creating Job Requisitions:

• Use the "Create/Post" operation instead of "Upsert Multiple".

KBA 3508419 - How to Mass Create Job Requisitions using Integration Center - Recruiting Management

KBA 2771951 - How to update Job Requisition fields using Integration Center - Recruiting Management

RCM, error, deleted, not valid, integration center, api, odata, mass upload, job requisitions, template, index, field association, field mapping, mass create job requisitions , KBA , LOD-SF-RCM-API , Webservices & APIs , LOD-SF-RCM-JOB , Job Postings & Requisitions , LOD-SF-RCM-INT , Integration Center & Intelligent Services , Problem