Task "Synchronize this object" is missing in Tasks pannel

Hello experts.

I am turning to you becouse I'm running out of ideas as to why there is a task "Synchronize this object" present in DEV environment, but not in PROD environment.

We created a first time installation at our customer in DEV environment and configured everything that has to be done for the first phase. We transported the DEV configuration to PROD environment through Database transporter since it was the first phase and a clean installation in PROD envrionment. We changed the sync projects connection strings and ran the synchronization projects. Everything went smoothly except for one thing. The main functionality that is now missing in PROD environment is the task "Synchronize this object" for target systems of AD, AAD and Exchange online and we are struggling to find the reason why and how to (re)configure it.

Has this ever happenned to anyone and how did you solve this issue?

Br,

Tadej

  • The task "Synchronize this object" will only appear if it can find a single object operation entry named 'Read' for the specified target system.
    Look under: Process Orchestration\Single object operation
    and find 'Read' entry 

    Or use this example query to compare both environments:
    select * from DPRobjectOperation oo, DPRRootObjConnectionInfo ci
      where oo.UID_DPRSystemConnection  = ci.UID_DPRSystemConnection
        and oo. Name = 'Read'
                and ci.ObjectKeyRoot like '<Key><T>ADSDomain</T><P>%</P></Key>'
        and oo.UID_DialogTable = 'ADS-T-ADSAccount'

  • Hi Niels.

    I checked the records in Single object operation and it is completely empty in my PROD environment. Did we somehow miss this with transferring configuration from DEV to PROD environment and how can we fix this?

    Br,

    Tadej

  • Hi Tadej,

    The single object operations are normally added during the creation and configuration of a new synchronization project.
    You could re-create them by hand in Designer.
    But maybe better verify your method of transferring configs with an OneIM consultant as there are different ways to do this.

  • Hi Niels,

    We played a little with this issue since it was the first time it happened to us in a project.

    1. We tried to recreate a single object with READ function for an ADSAccount with the same parameters as on DEV environment -> Commit & Compile -> Checked the Tasks panel on user accounts and the task was present and the test run was successful.

    2. Deleted the newly created record on PROD environment and went back to DEV environment. We ran the Database transporter and selected the option "Transport selected objects and dependencies" -> navigated to table DPRObjectOperation -> selected all records and the chose the option "The selected objects and dependencies will be added to the transport file. Relations are processed in the target database on import. Redundant object will be deleted."

    It took a while to create the transport package (aprox. 1h 20min).

    3. We ran the Database transporter in PROD environment and imported the Transport package.

    It also took a while to import the transport package (aprox. 50 min). Also, for this kind of transport package, all connections to the database have to be terminated (Transporter shows you which user has open OneIM tools and you have to notify users that they close the tools or you have the option to forcibly close the sessions). We did not want to take risks for users to try to establish connection through the tools mid transport so we notified them and when all the sessions were terminated, the transport package was successfully imported.

    The issue seems to be resolved as all the functionalities for read are present in the Tasks panel and the first "Synchronize this object" tests were done successfully.

    We still do not know how and why this happenned, as the synchronization projects on PROD envrionment were created manually at first but later removed before the initial configuration transport (we made some changes to the sync projects in DEV environment and wanted to transport them to PROD instead of manually do the changes that were done in DEV envrionment). But i guess this issues is something we will take a look at another time if it happens again.

    Thank you for all the help.

    Br,

    Tadej