Transform to find Source Manager

We have a unique situation where the Account Name and Account ID will be changing for all users in our Authoritative HR Source. Once I change the attribute, I know the source accounts will be deleted and recreated with the new ID, which is ok because we have no entitlements and the account correlates as expected in Non-Prod.

The issue I am facing is continuing with the Manager field on the Identity. Since the Identity Account Name will not be updated (without losing all logs and Events), how can I update the Identity Profile to ensure that the Manager attribute can look at an attribute in the HR source and transform it to the actual Account Name of that Manager? I’ve tried using Get Reference Identity Attribute but it seems limited to Identity Attributes.

Are you able to give an example? Are you looking to map a particular attribute from the manager’s account. Or specifically the value that is the Account Name on that source?

If it is a particular attribute, then map that attribute for all users to an Identity Attribute. Then use the Get Reference Identity Attribute rule as you mentioned to get the manager’s value.

Here is a screenshot of a test user in my dev environment. From my understanding, I need to match the Manager Name (manager) attribute in the Identity Profile to the ACCOUNT NAME (AGA234 in this example) in order for that Manager field on the Identity to populate. The problem is that AGA234 will no longer be an attribute that comes from our HR source due to a change in the Unique ID they are using so I believe I need to try to use a Transform in the Identity Profile to find the manager based on a different attribute and return the ACCOUNT NAME, which is ‘name’.

You should not need to lookup the Account Name to correlate the manager. This should be done on the authoritative source either using a simple mapping (SUPERVISOR_ID == EMPLID) or a manager correlation rule.

The mapping of the “manager” Identity Attribute is not used to determine the manager. Though the mapping does need to be populated with something in order for the manage logic to be calculated.

Once the manager is correlated to the direct report you can use the Get Reference Identity Attribute:

{
    "id": "70cad419-95dd-4a59-97a2-cb36a5b650d9",
    "name": "Manager DN",
    "type": "rule",
    "attributes": {
        "name": "Cloud Services Deployment Utility",
        "operation": "getReferenceIdentityAttribute",
        "uid": "manager",
        "attributeName": "<technical name of manager's Identity attribute>"
    },
    "internal": false
}

Hi Edward, Thank you for that information. I must have been doing something wrong with the Manager Correlation on the HR Source, which I have updated to use the Employee Number and the Reports To New ID. I updated the Employee Number attribute on the Identity Profile to look at the new attribute on the new source, and now I can see it working as expected. Thanks again!

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.