Symptom
When performing an OData API call to query the values for a certain field, the payload returns a "null" value, even if there is data stored for that field.
Environment
SAP SuccessFactors Recruiting Management
Reproducing the Issue
- Start a query by selecting JobOffer as an entity and selecting the Offer Approval
- From the payload, it's possible to see the data null:
"entityName": "JobOffer",
"payload": [
{
"cust": null,
"__metadata": {
"type": "SFOData.JobOffer",
"uri": "JobOffer"
}
Cause
The affected field is designed with different sources established within different Offer Detail Templates. In one Template we have it defined as "Application", while inside another, the same field ID will get the value derived from "Requisition".
When querying the entity JobOffer, values are inherited depending on the template-type defined in each Offer Detail Template, as per Guide:
"The JobOffer entity inherits some fields from JobApplication and from Job Requisition. These fields are defined on the offer template at provisioning. They’re initially filled with its inherited value, and keep these values if not edited or changed during the creation operation."
Resolution
In order to resolve it, would be necessary to either fill the value from all sources used (Application and Requisition) or change the sources to be equal in all templates for that field (use only template-type=job-application for example).
For more details, please refer to our Guide section for JobOffer Entity: JobOffer.
Keywords
odata API, no value, joboffer, offer approval, null field, empty field , KBA , LOD-SF-RCM-CAO , Candidate Offers, Offer Letters , Problem