Provisioning through One Identity Manager connector

Hello experts,

I'm trying to set up the provisioning mechanism from the table Person to a custom table CCC_Person_Reporting from the same DB, through a simple One Identity Manager connector. For now I would like to just provision the INSERT.

I created the connector, the single object operation and the process (taking inspiration from the ADSAccount insert for example), but I'm having hard times understanding how to use the script DPR_GetAdHocData.

In the parameter "rootObjectKey" I tried many alternatives, for example the object key of the DPRSchema One Identity, but everything goes in error. So, what "rootObjectKey" should I use? 

If this can help, the error I get when I try the script is: "Connection data for <object key> could not be detected".

Thank you for your help,

Lucrezia

Parents Reply Children
  • Hello Markus,

    yes, the single object operations were created following the documentation. 

    I set the Base Object of the Sync Project as the base table CCC_Person_Reporting, which is the target table of the synchronization.
    In the script, I tried using the XObjectKey of the CCC_Person_Reporting but I get the error "Exception has been thrown by the target of an invocation. Object reference not set to an instance of an object".
    If I use the XObjectKey of the table Person, I get the error "Exception has been thrown by the target of an invocation. Connection data for <XObjectKey Person> could not be detected."

    What do you think?
    Thank you,
    Lucrezia

  • As the table CCC_Person_Reporting is the "target system" in your use-case you need to configure the base object to the table Person. At least this is what I believe is one of the issues here.

  • Hello,
    I've put the CCC_Person_Reporting table (target) as the base object of the Sync Project, and the Person table (source) as the object table of the single object operation. That didn't solve the problem.

    After some debugging of the scripts involved in the process (DPR_GetAdHocData and others), we were able to determined that the value "UID_DPRProjectionConfiguration" (the Sync Project's workflow) was not computed. Unfortunately, we couldn't understand why, but we inserted it manually and the provisioning worked.

    We will contact support to solve this issue.
    Thank you