Hi all,
We're trying to request all non-anonymized candidates from a SuccessFactors instance using OData, so we're using a filter on the anonymized property.
The OData filter that we're trying to use is the following (in a Sales demo system):
https://apisalesdemo8.successfactors.com:443/odata/v2/Candidate?$filter=anonymized eq 'Non-anonymized'
But we don't get any results back.
Interestingly enough we discovered that this works:
https://apisalesdemo8.successfactors.com:443/odata/v2/Candidate?$filter=anonymized eq '0'
Returns:
{
"d": {
"results": [
{
"__metadata": {
"uri": "https://apisalesdemo8.successfactors.com:443/odata/v2/Candidate(361L)",
"type": "SFOData.Candidate"
},
"candidateId": "361",
"candidateLocale": null,
"cellPhone": "650 645 2000",
"partnerMemberId": null,
"anonymized": "Non-anonymized",
"lastModifiedDateTime": "/Date(1258745682000+0000)/",
"homePhone": null,
"usersSysId": null,
"visibilityOption": false,
"publicIntranet": false,
"city": "San Mateo",
"consentToMarketing": null,
...
So it looks like this might be based on an internal value of 1 and 0? But the response returns 'Non-anonymized' as the value.
We thought it might be based on the raw value but when we tried the following:
https://apisalesdemo8.successfactors.com:443/odata/v2/Candidate(361L)/anonymized/$value
it still gave us 'Non-anonymized' instead of '0'.
We still have to purge some data so that we can test if eq '1' works for anonymized values.
Does anybody have any idea why this is happening? Tried searching for documentation but found nothing.