Fields Being Read as Null in Rest Connection

[Ryne_G]

We have a rest connection to a partner company Azure AD instance so that we can pull in the user emails and provide guest accounts to our Azure environment. This same connection format has been used successfully with three other companies. This time when running the user import job all employeeid values are coming through as null. The employeeid value is coming through when doing the same call from postman.  It also looks like the id value being pulled is Saviynt generated where as when doing the call in postman we can see the actual ID value from the source Azure environment.

test connection is successful.

This is the current importuser json

{
"connection": "userAuth",
"url": "https://graph.microsoft.com/v1.0/users?$$select=Id,employeeid,mail",
"httpMethod": "GET",
"httpHeaders": {
"Authorization": "${access_token}",
"Accept": "application/json"
},
"statusConfig": {
"active": "true",
"inactive": "false"
},
"colsToPropsMap": {
"employeeid": "employeeId~#~char",
"email": "mail~#~char"
},
"userResponsePath": "value",
"pagination": {
"nextUrl": {
"nextUrlPath": "${(response?.completeResponseMap?.get('@odata.nextLink')==null)? null : response?.completeResponseMap?.get('@odata.nextLink')}"
}
}
}

We are seeing the following in Log Viewer when running the import job. The job is using employeeid as the reconciliation field.

2023-10-16T10:06:36-04:00-ecm-worker-services.ImportSAvDataUserService-quartzScheduler_Worker-9-f57fw-ERROR-Missing employeeid for the record# 508 : [SAVGEN-8081640055084222609, null, TYork@###.com]

2023-10-16T10:06:36-04:00-ecm-worker-services.ImportSAvDataUserService-quartzScheduler_Worker-9-f57fw-DEBUG-Proceed to Import for records - > [SAVGEN-8081640055084222609, null, TYork@###.com] : false

2023-10-16T10:06:36-04:00-ecm-worker-services.ImportSAvDataUserService-quartzScheduler_Worker-9-f57fw-DEBUG-Not Importing user - either username attribute not found or if vendor is there then user doesnt have access to import the vendor-[SAVGEN-8081640055084222609, null, TYork@###.com]

(I have removed the domain for the email addresses)

[Saathvik]

@Ryne_G : As far as I know you cannot do user import without username mapping as it is mandatory. In your JSON I don't see username mapping. Can you add username mapping and see if that works? Also other connections you mentioned are working were also not having username mapping?

[Ryne_G · Accepted solution]

The other connections being used for the same purpose do not have username mapped either. The jobs being run involving all of these connections is specifically to update user only to make email match the legacy company email. The identity objects are still created from a Workday import exclusively.

I updated to include username and had the same issue. Reviewed the URL and saw that it contained an extra "$" for pulling the user information. This was removed and the user import successfully populated the employeeid and updated the expected emails based on the employeeid reconciliation field used in the job

"url": "https://graph.microsoft.com/v1.0/users?$$select=Id,employeeid,mail",