Symptom
When creating application via ODATA API, we are unable to insert the standard job application “startDate” date field. While custom date field can be inserted however once the application is created, we can upsert the startDate field
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental
Environment
SAP SuccessFactors Recruiting Management
Reproducing the Issue
- Using any existing candidate, Add fields startDate and custom date field in this creation API payload and create new application via IC or ODATA API,
- The standard startDate field remains blank but the custom field gets inserted.
- Repeat the process for already created application
- Confirm that the "startDate" field is now updated
Cause
This is expected behavior
Resolution
The startDate refers to the start date of the application. Many other application properties are calculated based on this startDate field value like timeToHire etc. There could be situations were recruiter wants to start the application at a later time even though the application is created. Hence, this not populated at the time of application creation and is up to the recruiter to populate this via the update flow of the application.
So, this behavior aligns with the application creation workflow, where the "startDate" field is left blank to allow flexibility for recruiters to set it during the update flow.
If the "startDate" field needs to be updated, it must be done after the application is created using the update flow.
Keywords
startDate, job application, integration center, ODATA API, sap successfactors recruiting, job requisition, application creation workflow, custom date fields, update flow, sap successfactors, mass upload, integration center job, standard field, recruiting management. , KBA , LOD-SF-RCM-INT , Integration Center & Intelligent Services , LOD-SF-RCM-API , Webservices & APIs , LOD-SF-RCM-APP , Applicants and Job Applications , How To
SAP Knowledge Base Article - Public