Provisioning through One Identity Manager connector

What is the use-case to use a synchronization project for this instead of an on-saved script (synchronously) or a process with a HandleObjectComponent? 

The reason is we need to handle insert, update, and delete, so it is much simpler in the way connector works. Another reason is that for now we have just 10 fields to synchronize between the two tables, but in future integrations, these fields will increase and the parameters of a process are not very handy for that.

We thought about the connector but we're open to better solutions. Have you got any suggestion? 

Thank you for the answer,
Lucrezia

Understood.

Did you create the single object operations as described here https://support.oneidentity.com/de-de/technical-documents/identity-manager/9.2/target-system-synchronization-reference-guide/45#TOPIC-2079500 ?

Regarding the rootObjectKey, you need to point it to the baseobject defined in your synchronization project. In your case, I assume you do not have a real root object (like a AADOrganization or an ADSDomain) defined as the baseobject but the DialogTable entry for the Person table. This would be the XObjectKey you need to use.

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.

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