The synchronization of the following two commands (on the OOTB Data Mapping templates) is scheduled to run daily:
- Get Activity Data from P6
- Send Activity Data to P6
Note: For details, see the "Data Mapping Templates" section.
Synchronization can be performed:
- From Unifier by executing the "Get Data" or "Get Activity Sheet Data" commands from the "Activity Sheet" log or the Shell log.
- From Gateway, manually.
The Unifier Provider performs a check to see if the Unifier Project is linked to the corresponding P6 Project.
- If the Unifier Project is not linked to the corresponding P6 Project, you need to establish the link.
- If P6 does not have a corresponding project, then a message will notify you that the project has not been created in P6.
To ensure a successful synchronization, do the following:
- Set the Shell attribute DE =
uuu_integrated_withto P6.Note: If the attribute was missing, after this setup the integration will take place.
- Receive the Activity Sheet data from Gateway and:
- If an "Activity Sheet" does not exist in Unifier, create the "Activity Sheet," populate the fields with the data received, and name the sheet as:
<P6 project name>. - If an "Activity Sheet" exist in Unifier, update the "Activity Sheet" with the data from Gateway.
- If an "Activity Sheet" does not exist in Unifier, create the "Activity Sheet," populate the fields with the data received, and name the sheet as:
You need to perform the steps above to create the "Activity Sheet" within Unifier Shells for the first time, only. Once you create an "Activity Sheet," the hourly synchronization updates the "Activity Sheet" with the latest data received from Gateway.
When projects between Unifier and P6 are linked for the first time, Gateway ensures that a P6 Project attribute that is integrated is checked.
If a "Get Activity Data from " synchronization is performed, but the P6 Project that must correspond to the Unifier Project is not found by Gateway, then Unifier will generate an error-message.
Sending Activity Sheet data to P6
When you synchronize, the Unifier Provider performs the following:
- Checks to ensure that the Unifier Project contains an "Activity Sheet."
- If an "Activity Sheet" does not exist, then the system generates an error-message.
- If an "Activity Sheet" exist, then you can continue on with pulling (receiving) data.
- Pull all updated "Activity Sheet" data by way of Reverse Auto-Population since the last "Send Activity Data to P6" synchronization. You can send the updated "Activity Sheet" to Gateway in Portable Database Image (PDI) format.
- If the "Activity Sheet" has not been updated by way of Reverse Auto-Population, then you do not need to send data to P6.
- If you add a DE to a Data Mapping template that is read-only in P6, then the system generates an error-message.
Additional information about synchronization
- If an Activity Type, in a Schedule, is set as “Start Milestone,” then P6 does not allow you to update the "Actual Finish Date." If you proceed with updating the "Actual Finish Date," then you generate inconsistent data.
- If an Activity Type, in a Schedule, is set as “Finish Milestone,” then P6 does not allow you to update the "Actual Start Date." If you proceed with updating the "Actual Finish Date," then you generate inconsistent data.
- You must define the filter condition before you filter the Unifier Project using the "Send Activity Data to P6" synchronization command.
Note: If a filter condition is defined in Business Flow, but a filter condition is not defined in the synchronization, Gateway will not know which Unifier Project to send data from. As a result, filter condition must be defined within the synchronization itself.
Connectivity issues with Gateway or incorrect Gateway parameters will cause synchronization to fail. Use History, Admin mode, to see the list of failed synchronizations, if any.
Criteria for successful data exchange
Ensure that the fields ("Update Activity Sheet from P6" and "Send Activity data to P6") in the Data Mapping templates are not overlapping and a field that is set to map from P6 to Unifier is not added to the "Send" template.
Note: The OOTB Data Mapping templates are designed in a way that the fields are exclusive; therefore, when you edit a Data Mapping template, ensure that you keep the fields that are exclusive intact.
If you use DE = uuu_int_p6_project_id for linking P6 and Unifier projects, when the "Project ID" field in P6 is updated, then the "P6 Project ID" (uuu_p6_project_id), field in corresponding Unifier Shell, must be updated manually.