Guidelines for best results synchronizing project schedules between Microsoft Project and Daptiv:
Do not break the synchronization link (override checkout). If the synchronization link is broken, either:
Note: If you attempt to establish a new link between the current Microsoft Project file and the same PPM workspace, the tasks existing in both locations will be carried forward, resulting in a duplication of tasks.Once a PPM workspace is locked for synchronization with ProjectTransit, all schedule changes must be made within Microsoft Project – users will not be able to edit the tasks within PPM. Note, however, that task updates will still be performed within PPM. This allows all task assignees to enter the work that they have performed and update the % Complete or ETC.
Note that the Daptiv PPM values of Actual Start, Actual Finish and Actual Work are synchronized to custom fields within Microsoft Project. This is necessary in order to avoid having these numbers overridden by the Microsoft Project scheduling engine. Thus, it is recommended that you:
- Within Microsoft Project, do not show or use the native Actual Start, Actual Finish and Actual Work fields. Instead:
- Rename the “Date 1” and “Date 2” custom fields to be “Actual Start” and “Actual Finish” respectively. Show these fields.
- Rename the “Number 10” custom field to be “Actual Work”. Show this field.
If your enterprise uses SAML Single SignOn to enable you to access Daptiv PPM without logging in, please note that this authentication mechanism does not work with ProjectTransit. You will need to use the standard PPM login credentials to use ProjectTransit.