Account ID not loading for WebServices connector

Hello,

I’m having issues loading account data post creation. I’m using SailPoint’s API (loopback) to create accounts on a NELM source. I have a rule deployed that generates the UID and when the account is successfully created on NELM (all the data is populated correctly) the account on the loopback source doesn’t have the account ID and shows as “–” in the Identity’s account list.

I have checked the processedResponsecObject and the mapping is correct! I can see: accountName=F00351 but on the sailPoint interface, the accountName shows as “- -” but the other attributes are populated. I have tried to duplicate the attribute and mark it as “account Name”, now that attribute gets populated but the accountName (account ID) remains empty and the account on the loopback source looks like this:

accountName:null
accountName2:F00351
...

When I run an aggregation, the account is loaded correctly, but I don’t want to rerun an aggregation after each account create.

Anyone had a similar issue ?
Thank you,

The Account Create API :

POST /beta/non-employee-records
{
  "accountName": "$plan.nativeIdentity$",
  "firstName": "$plan.firstName$",
  "lastName": "$plan.lastName$",
  "sourceId": "NELM_SOURCE_ID_HERE",
  "manager": "JOHN_DOE",
  "email": "[email protected]",
  "phone": "+33 123456789",
  "startDate": "2025-03-11T02:01:00Z",
  "endDate": "2325-02-05T23:00:00Z"
}

The source schema has accountName (Account ID and account Name), firstname and lastname.

My Prov policy create:

{
    "name": "Account Create",
    "description": null,
    "usageType": "CREATE",
    "fields": [
        {
            "name": "accountName",
            "transform": {
                "attributes": {
                    "patterns": [
                        "$userNameValue"
                    ],
                    "userNameValue": {
                        "type": "rule",
                        "attributes": {
                            "name": "Generate account ID"
                        }
                    },
                    "sourceCheck": true
                },
                "type": "usernameGenerator"
            },
            "attributes": {
                "cloudMaxUniqueChecks": "50",
                "cloudMaxSize": "61",
                "cloudRequired": "true"
            },
            "isRequired": false,
            "type": "string",
            "isMultiValued": false
        },
        {
            "name": "firstName",
            "transform": {
                "type": "identityAttribute",
                "attributes": {
                    "name": "firstname"
                }
            },
            "attributes": {},
            "isRequired": false,
            "type": "string",
            "isMultiValued": false
        },
        {
            "name": "lastName",
            "transform": {
                "type": "identityAttribute",
                "attributes": {
                    "name": "lastname"
                }
            },
            "attributes": {},
            "isRequired": false,
            "type": "string",
            "isMultiValued": false
        }
    ]
}

Hi @WhiteBat ,

I’m also facing the similar issue . We have use web service connector to connect SAP source . Everything looks good except the account id is shown as – . If anyone is facing this issue do let us know.

Thanks,
Naveen

Hi @naveenkarthikkrk

For create account , in response mapping , map the account name attribute with respective response mapping and check .

Or

Try putting a get single account operation after create operation

1 Like

I have added the mapping and still the attribute is empty. The attribute accountName is mapped with accountName2 and accountName but the value only shows in accountName2.

For the get single account operation, I have it already and still the accountName doesn’t load, if I run a single account aggregation I get an error because it uses the accountId attribute as a parameter in the getOpbject.nativeIdentity which is accountName and it’s empty.

Hi @WhiteBat

Remove root path and try direct mapping in Create Op
for example:

accountName : $. accountName
and so…

Hello @sidharth_tarlapally,

I don’t have a root path configured. And the mapping seems to be correct because when I debug the processedResponseObject the data is mapped correctly. It seems that SailPoint clears the accountId value after provisioning.

I saw that this issue is faced by many others and the only solution is to run an aggregation.

Thank you for your assistance.

1 Like

Hi

Hope this post will help you resolve