Error while SailPoint provisioning is looking for salesforce managerid

[osmanmohammed]

Hi All,
we have salesforce native connector setup
all the operations( create/update) are functioning as expected but we are facing issue while creating account for “field sales manager” AP

[jesvin90 (Jesvin Joseph)]

Hi @osmanmohammed,

Have you checked if the manager ID that you are passing from IDN actually exist as a user in Salesforce.?

This looks more like a Salesforce issue and would be better to work with Salesforce team to check what would be stopping the account creation.

[tysremi (Remi Tys)]

What do you mean with ‘native’ connector?
The VA-based connector? (and not the SaaS connector?)

In either case, check the logs for specifics…
Maybe indeed the specified manager id does not exist in Salesforce, or the manager of the user is empty (causing your transform on identity attribute to fail)

[osmanmohammed]

we have 20/21 access profiles that does create / update accounts in Salesforce based on the above manager configuration.

we were not able to debug what is the root cause for this failed attempt only for " Field sales Manager" AP.

on the other hand i want to know what does the below rule {Cloud Services Deployment Utility" does in account creation ?

{
    "id": "71dfhbsdhsbdbjdfb",
    "name": "W3-Main-SalesforceManager",
    "type": "rule",
    "attributes": {
        "uid": "manager",
        "name": "Cloud Services Deployment Utility",
        "attributeName": "salesforceUserId",
        "operation": "getReferenceIdentityAttribute"
    },
    "internal": false
}

[jesvin90 (Jesvin Joseph)]

Hi @osmanmohammed,

This transform finds the manager of the Identity and populates the manager’s Identity attribute value - salesforceUserId.

Here is the transform details :

Get Reference Identity Attribute | SailPoint Developer Community

Does the Salesforce access profile contain multiple entitlements.? If so it could be a particular entitlement that specifically requires the manager value.?

[osmanmohammed]

it was resolved, the issue was we renamed source and when we did a reset it worked.