Manager Correlation not working on Web Services SaaS source

Hello! In my dev tenant, I have a Web Services SaaS source connected to an AirTable that I’m using as my authoritative source. This source has an id field (mapped to the identificationNumber identity attribute, aka Employee Number), a manager_id field (mapped to the manager identiy attribute, aka Manager Name), and a manager_name field, among others. I’ve tried configuring the manager correlation on the source accordingly:

But I’m not having any luck. The manager_id and manager_name attributes are present on the accounts, but the Manager is still showing as blank in the Identity. I’ve tried unoptimized aggregations, source resets, identity refreshes, deleting the identities entirely… all no joy. Any suggestions?

Hey Mark,

Have you tried applying a trim transform on the values in the Identity Profile?

In the past, I’ve seen whitespace around IDs to cause issues with correlation rules.

May not be your solution, but its always good to rule it out.

Best Wishes

Ryan

Thanks for the suggestion, @Mccarney! Unfortunately, that’s not the issue here. Here’s an example of what an identity/account looks like. I’m curious if it’s because the manager_id attribute is coming in as an array for some reason? It’s not configured as a multi-valued attribute though, so I’m not sure why it would be an array or if that’s just normal.

    {
        "authoritative": true,
        "systemAccount": false,
        "uncorrelated": false,
        "features": "ENABLE, PASSWORD, UNLOCK, PROVISIONING",
        "cloudLifecycleState": "active",
        "identityState": null,
        "connectionType": "direct",
        "uuid": null,
        "nativeIdentity": "2",
        "description": null,
        "disabled": false,
        "locked": false,
        "type": null,
        "manuallyCorrelated": false,
        "hasEntitlements": true,
        "sourceId": "979f89fb3ccb4a5ea71c7a9d2db516d2",
        "sourceName": "Star Wars - AirTable",
        "identityId": "d7c2f9deecae44e7aa2e55b620e0f59c",
        "identity": {
            "type": "IDENTITY",
            "id": "d7c2f9deecae44e7aa2e55b620e0f59c",
            "name": "C-3PO"
        },
        "sourceOwner": {
            "type": "IDENTITY",
            "id": "2618f05c3edd48d49ff1ab04446d9f89",
            "name": "SailPoint Services"
        },
        "attributes": {
            "end_date": null,
            "IIQDisabled": false,
            "homeworld": [
                "Tatooine"
            ],
            "manager_id": [
                "1"
            ],
            "IIQLocked": false,
            "id": "2",
            "department": "Resistance",
            "first_name": "C",
            "height": "167",
            "start_date": [
                "1977-05-25"
            ],
            "films": [
                "A New Hope",
                "The Empire Strikes Back",
                "Return of the Jedi",
                "The Phantom Menace",
                "Attack of the Clones",
                "Revenge of the Sith",
                "The Rise of Skywalker",
                "The Last Jedi"
            ],
            "edited": "12/20/2014 9:17:50 PM",
            "created": "12/10/2014 3:10:51 PM",
            "active": "true",
            "last_name": "3PO",
            "hair_color": "n/a",
            "manager_name": [
                "Luke Skywalker"
            ],
            "species": [
                "Droid"
            ],
            "starships": null,
            "name": "C-3PO",
            "alignment": "good",
            "status": "active"
        },
        "origin": null,
        "ownerIdentity": null,
        "ownerGroup": null,
        "id": "689f6598068f4b80848f3f59cdd2d13e",
        "name": "C-3PO",
        "created": "2024-08-14T13:56:54.647Z",
        "modified": "2024-08-14T14:04:28.501Z"
    }

Update: this was, in fact, because it was coming through as an array. After updating the Attribute Path on the Accounts Aggregation operation for manager_id to manager_id[0], I’m now seeing managers populate successfully :slight_smile:

1 Like

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