3447356 - The JobApplication and Candidate entities contain fields where nullable=false but shows null values in get query.

Within the SuccessFactors ODATA Metadata, The JobApplication and Candidate entities contain several properties (fields) where nullable=false.

Performing ODATA GET calls on those properties show null values. This seems to be in conflict with the metadata.

SAP SuccessFactors Recruiting Management

Run a get query on certain entities JobApplication and Candidate and verify the OData API dictionary,

you can see these entities have the property nullable=false.

But, in the response you can see that these fields have null value.

We have confirmed this with the Engineering team and :

Nullable means: SuccessFactors do not allow these properties (fields) to be changed from a value to null value via ODATA.

The properties (fields)  value CAN be null. They can start off as null, or the application may be able to set the value to null.

This does not mean that when we run a GET query on these properties it should not be null.

nullable, false, jobApplication, candidate, candidateLight, nullable=false, OData API data dictionary, OData. , KBA , LOD-SF-RCM-API , Webservices & APIs , Problem

SAP SuccessFactors HXM Core 2305 ; SAP SuccessFactors HXM Core 2311 ; SAP SuccessFactors Recruiting all versions