Simple lookup transform only returning default values

I have created an account provisioning policy for Active Directory, which is working great. I’m adding some fields that reference an identityAttribute (which was calculated with its own transform) and then replaces that value with a different static value using a lookup table. When I test, I am not getting any errors, it does fill in the required fields in Active Directory, but no matter what the input is, the output is always the default entry.

Original Input from HR source: “CA - NO Vets - Branch”
identity Transform:

{
    "id": "8af36cb6-a5a6-4810-b9ac-47222ac947dd",
    "name": "Region from OrgUnit",
    "type": "substring",
    "attributes": {
        "begin": -1,
        "end": 2
    },
    "internal": false
}

Output to identityAttribute “Organization” = CA

^All of that works fine. Now, I want to take the human readable value of CA and convert it to it’s corresponding code for the AD attribute “businessCategory”.

Provisioning Policy:

 {
            "name": "businessCategory",
            "transform": {
                "type": "lookup",
                "attributes": {
                    "input": {
                        "type": "identityAttribute",
                        "attributes": {
                            "name": "Organization"
                        }
                    },
                    "table": {
                        "CA": "88",
                        "CM": "70",
                        "FN": "40",
                        "IT": "35",
                        "LG": "41",
                        "LN": "60",
                        "LS": "50",
                        "PR": "80",
                        "default": "00"
                    }
                }
            },
            "attributes": {},
            "isRequired": false,
            "type": "string",
            "isMultiValued": false
        },

Output to businessCategory in AD: 00

Tested with multiple accounts and no matter the input, I always get 00 as the output. Any ideas? This seems like a really simple transform and I basically copy/pasted from the documentation. I was really not expecting anything to go wrong.

Hi @Shaebates ,
Greetings of the Day!

Kindly note that please check the identity attribute and modify the technical name for organization then you will get the exact output.

Let me know for any queries

Thank You
Mahesh M

Hi @Shaebates ,

Check the input part of business category, I think the name of the identity attribute you have used might be wrong.

"input": {
                        "type": "identityAttribute",
                        "attributes": {
                            "name": "Organization"
                        }
                    }

Try using the technical name of the identity attribute organization.
For your reference, I have attached the screenshot.

Thanks!

Hi @Shaebates,

Identity attribute name should be name/technical name of the attribute, I guess Organization is display name.

Technical name is always camel case. I think “organization” is technical name

{
            "name": "businessCategory",
            "transform": {
                "type": "lookup",
                "attributes": {
                    "input": {
                        "type": "identityAttribute",
                        "attributes": {
                            "name": "organization"
                        }
                    },
                    "table": {
                        "CA": "88",
                        "CM": "70",
                        "FN": "40",
                        "IT": "35",
                        "LG": "41",
                        "LN": "60",
                        "LS": "50",
                        "PR": "80",
                        "default": "00"
                    }
                }
            },
            "attributes": {},
            "isRequired": false,
            "type": "string",
            "isMultiValued": false
        },

-Vasanth

1 Like

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