SAP Success Factor Activities - Unable to Query Email Address

Hello,
I am trying to use success factor activities to get the email address, email type and IsPrimary. I am using ‘Search Record’ activity and passing the parameters in expand and select attribute, however i do not get the response in different columns in data table.
image

select - {“userId”,“firstName”,“empInfo/personNav/emailNav/isPrimary”,“empInfo/personNav/emailNav/emailAddress”,“empInfo/personNav/emailNav/emailType”}

expand - {“empInfo”, “empInfo/personNav”, “empInfo/personNav/phoneNav”, “empInfo/personNav/emailNav”,“empInfo/personNav/personalInfoNav”}

I am writing the output datatable into excel but only 3 columns are present. It does show emailid, email type in different columns.
image

I am writing the output datatable into excel but only 3 columns are present. It does show emailid, email type in different columns.
image

Hi Tarun - can you please validate which version of the activity pack you are using? I ask in that we made some fixes to how this works in the most recent version.

It is 1.1.7688.14923. Same problem in fetching manager first name,lastname etc. The expand does not seem to work.

Hi - can you post the xaml you are running? It would help us understand the issue.

Hello,
Apologies i can not post the xaml as it has sensitive connection details. Basically, i am trying to get the manager first name, last name, userid and email details.

The json response from success factor is below:
Request:
https://api4preview.sapsf.com/odata/v2/User?$select=firstName,lastName,loginMethod,username,status,businessPhone,email,hireDate,teamMembersSize,country,manager/firstName, manager/lastName,manager/userId&$filter=userId eq ‘30147’&$format=JSON&$expand=manager

response:
{
“d”: {
“results”: [
{
“__metadata”: {
“uri”: “https://api4preview.sapsf.com:443/odata/v2/User(‘xxx’)”,
“type”: “SFOData.User”
},
“firstName”: “xxxx”,
“lastName”: “xxx”,
“country”: “xxxx”,
“hireDate”: “xxxxx”,
“teamMembersSize”: xx,
“loginMethod”: “xxx”,
“businessPhone”: null,
“email”: “xx@sap.com”,
“username”: “xx@xxx.com”,
“status”: “t”,
“manager”: {
“__metadata”: {
“uri”: “https://api4preview.sapsf.com:443/odata/v2/User(‘xxxx’)”,
“type”: “SFOData.User”
},
“userId”: “xxx”,
“firstName”: “xx”,
“lastName”: “xx”
}
}
]
}
}

Configuration done in Select user in Uipath to get the manager first name, last name.

Select value:{“firstName”,“lastName”,“loginMethod”,“username”,“status”,“businessPhone”,“email”,“hireDate”,“teamMembersSize”,“country”,“manager/firstName”, “manager/lastName”,“manager/userId”}
Expand: Manager

I am writing the output of above in datatable. However manager firstname, lastname and userid does not appear in separate columns. Only one column appear as manager instead 3 different columns. Similarly issue appears while retrieving email address, email type.

Secondly, while using the update activity how can i update the email id, username without nullifying other field. Currently, if i pass four fields - userid,username,emailid and status only for update using Update Record, all other fields like firstname,lastname, rid are getting updated as blank in success factor. Ideally, the update record activity should only update the fields which are getting passed in the input.

Hey @Dhandapani_Murugan , any thoughts on the above?

Hi Tarun - a few things if we may:

  1. The version of the activity pack you are using - 1.1.7688.14923 - isn’t officially supported and I’m not sure where you got it from. The latest supported is 1.1.1-preview which addresses the issue of your last comment about nullifying other fields, e.g. the patch that was released specifically should solve this problem.
  2. As for why the manager’s information isn’t added as additional columns to the datatable, the reason is that not all of that that can return from such a query is simple and can be translated to columns, so the object is returned as a jObject string. You can deserialize this to a jObject (via Parse) and then get the properties if you don’t want to do string manipulation.

Hope this helps,

Paul

@tgoel28 Tarun please let us know if the issue still persists or if you were able to resolve this?