Symptom
This article explains the behavior of the query return when running it against multiple job requisitions and expanding any team field. There is different behavior for the return when querying single job requisition and multiples.
When running a query for a single job requistion, the team field returns the users details for all the users and groups added to the respective team field. However, when running similar query to return multiple job requisitions, if a ground is added to the team field the returns are empty.
For example, when running the following query, the system will return the user information:
https://api4preview.sapsf.com/odata/v2/JobRequisition?$format=json&$expand=secondRecruiterTeam&$select=jobReqId,secondRecruiterTeam&$filter=jobReqId in 101
OR
https://api4preview.sapsf.com/odata/v2/JobRequisition(101)?$format=json&$expand=secondRecruiterTeam&$select=jobReqId,secondRecruiterTeam
Here is the return:
{
"d": {
"results": [
{
"__metadata": {
"uri": "https://api4preview.sapsf.com/odata/v2/JobRequisition(101L)",
"type": "SFOData.JobRequisition"
},
"jobReqId": "101",
"secondRecruiterTeam": {
"results": [
{
"__metadata": {
"uri": "https://api4preview.sapsf.com/odata/v2/JobRequisitionOperator(jobReqId=101L,operatorRole='W')",
"type": "SFOData.JobRequisitionOperator"
},
"jobReqId": "101",
"operatorRole": "W",
"lastName": "dummy",
"phone": null,
"fax": null,
"email": "dummy@sap.com",
"userName": "1234",
"firstName": "Dummy",
"isAdminSelected": true,
"usersSysId": "10001111",
"jobRequisition": {
"__deferred": {
"uri": "https://api4preview.sapsf.com/odata/v2/JobRequisitionOperator(jobReqId=101L,operatorRole='W')/jobRequisition"
}}}}}}
When running similar query to get more than one job requisition, the team field is empty:
https://api12preview.sapsf.eu/odata/v2/JobRequisition?$format=json&$expand=secondRecruiterTeam&$select=jobReqId,secondRecruiterTeam&$filter=jobReqId in 101,102
{
"d": {
"results": [
{
"__metadata": {
"uri": "https://api4preview.sapsf.com/odata/v2/JobRequisition(101L)",
"type": "SFOData.JobRequisition"
},
"jobReqId": "101",
"secondRecruiterTeam": {
"results": []
}
},
{
"__metadata": {
"uri": "https://api4preview.sapsf.com/odata/v2/JobRequisition(102L)",
"type": "SFOData.JobRequisition"
},
"jobReqId": "102",
"secondRecruiterTeam": {
"results": []
}
}
]
}
}
Environment
SuccessFactors Recruiting Management (RCM) - All versions
Reproducing the Issue
Query multiple job requisitions using any software like postman and expand the team fields.
Cause
The query will always return empty if a group is added to the team field. This is a known limitation we have in the product.
Resolution
Since it is a know limitation, as a workaround the user can manually add the same users the have for some specific group to the team field, this will make the return query show the team field information for each user. Adding just a group to the team field will not return any value as displayed in the symptom section.
According to the engineering team, changing this behavior will cause a high impact to API architecture and some considerable changes to the application. We do not have a target date to release such an enhancement.
If you have any business requirement that would justify such change, we always encorage our customers to raise this enhancement request to our community. Refere to the article with the necessary stes - 2230628 - Expected Behavior – Enhancement Request.
Keywords
expanding team fields, sourceTeam, recruitingTeam, secondRecruterTeam, originatorTeam, hiringManagerTeam, vpOfStaffingTeam, RCM-61128 , KBA , LOD-SF-RCM-API , Webservices & APIs , LOD-SF-RCM , Recruiting Management , Problem