Database Connector - CreateAccount - AccountID

[Community_User]

Originally posted on July 1 2020 at 14:29 UTC

We are in the process of configuring the database connector for one of our critical applications. We are successfully creating the new account, but need to map the accountID generated by the account creation so the entitlement tasks that are also generated work properly. How do we map the generated accountID back to the account in Saviynt? The subsequent tasks are failing due to not having the ID.

[Community_User]

Originally posted on July 2 2020 at 10:45 UTC

Hi Ryan,

Could you please explain your requirement a bit in detail. I did not understand what did you mean by mapping the accountID back to account in saviynt.

Thanks,

Ranjan

[Community_User]

Originally posted on July 2 2020 at 15:04 UTC

When we insert an account in the system database, it receives a generated integer id (primary key in database) that must be used when assigning entitlements. In the test connector, we can set the accountId property on Account based on a result in the response. We need to know how to do this in the database connector. Note that a reconciliation doesn’t work here since the tasks are already generated and running with the same provisioning job.

In REST Connector example:
{
"accountIdPath": "call1.message.user.id",
"dateFormat" : "yyyy-MM-dd'T'HH:mm:ssXXX",
"responseColsToPropsMap": {
"displayName": "call1.message.user.name~#~char"

},

This approach ensures that the Account, showing manually provisioned in Saviynt, has the correct key value from the time of creation.

[Community_User · Accepted solution]

Originally posted on July 3 2020 at 05:33 UTC

This feature is not yet available for Database Connector.

[Community_User]

Originally posted on July 6 2020 at 19:19 UTC

This item was marked as "answered", but I don't feel it really was. If the "feature' is not available, how does one configure the tasks so they don't error? They are generated at the same time as the account task and execute in the same job. We are using birthright roles to determine the required account/access.

[Community_User]

Originally posted on July 7 2020 at 04:56 UTC

This enhancement is in roadmap item for Database connector and would be available in a future release.