Hello @JamesMcClartyEY,
I believe the manager correlation has to be set on the authoritative source for the $identity.getManager()
to return the manager successfully.
I tested this in my environment using a Delimited source.
The source info looks like:
id | first_name | last_name | hire_date | manager | |
---|---|---|---|---|---|
100010 | [email protected] | Lewis | hamilton | 2020-12-12 | |
100011 | [email protected] | Frank | Williams | 2020-07-10 | 100010 |
100012 | [email protected] | Paddy | Lowe | 2020-09-20 |
The correlation is set Employee Number → manager where id in the table above is mapped to Employee Number.
I can then use the transform to get that managers attributes. When I am testing out and developing transforms I use the cc preview API.
I can test this out by retrieving the id of the employee whose manager’s attribute I want to pull and providing the transform to test.
{
"attributeTransforms": [
{
"attributeName": "personalEmail",
"type": "static",
"attributes": {
"value": "$identity.getManager().getAttribute('email')"
}
}
]
}
The response returned will look similar to below, there will be quite a lot more preview attributes. You can search for the attributeName you provided above, I used personalEmail
.
{
"displayName": "Frank",
"id": "2c918085840ffd580184155e40ea0966",
"meta": {
"created": "2022-10-26T17:36:49+00:00",
"modified": "2023-06-26T00:08:19+00:00",
"type": "identityProfiles"
},
"name": "Frank",
"previewAttributes": [
{
"messages": null,
"name": "personalEmail",
"previousValue": null,
"value": "[email protected]"
},
]
}
The getReferenceIdentityAttribute
from the Cloud Services Deployment Utility uses the same code to retrieve the manager identity so it does need to be correlated.