This is a project data field mapping template to send activity data sheet from Unifier to P6. This template maps fields of ‘Activity Sheet Attributes’ form to P6 ‘Activity’ object which get updated in Unifier through business process records.
Notes:
- Do not include fields that are common to this template and the 'Update Activity Data from P6' template. Otherwise incorrect data will be moved across applications.
- If an Activity Type in a schedule is a “Start Milestone”, then you cannot update the Actual Finish Date in P6. So, do not update the Actual Finish Date for this activity in Unifier and try to send it to P6. Otherwise, incorrect data will be moved between applications.
- If an Activity Type in a schedule is a “Finish Milestone” then you cannot update the Actual Start Date in P6. So, do not update the Actual Start Date for this activity in Unifier and try to send it to P6. Otherwise, incorrect data will be moved between applications.
- Project filter conditions must always be defined in the synchronization. If you define the condition in the business flow, instead of the synchronization, Gateway will not know which projects to send the data from.
The following fields are mapped:
Unifier | Gateway | P6 |
|---|---|---|
uuu_P6ActivityId | Id | Id |
uuu_P6ActualStart | ActualStartDate | ActualStartDate |
uuu_P6ActualFinish | ActualFinishDate | ActualFinishDate |