In the MSP New Driver, task Start Dates change to the Project Start Date when exported to MSP

Document ID : KB000047129
Last Modified Date : 30/05/2018
Show Technical Document Details

In the new MSP (Microsoft Project) Driver, some task Start Dates change to the project Start Date when the project is exported to MSP.

Steps to Reproduce:
1. Create a new project in PPM with a Start date of 5/1/2018
2. Create a new task in the project in PPM with a Start date of 5/4/2018
3. Export the project to MSP and observe the task Start date
Expected Results: Task Start date matches that in PPM (5/4/2018)
Actual Results: Task Start Date changes to the project Start date (5/1/2018)

CA PPM 14.x and higher using the MSP New Driver.
This is working by designed. In the MSP New Driver, tasks that are not started (% Complete equals 0%), are without specific constraints such as "Start no Earlier Than" or "Must Start On" and no dependencies are exported to MSP as the project start date. If there are dependencies involved, then this may cause tasks dates to be earlier/later depending on the dependency chain setup.

In the MSP legacy driver, tasks that do not match the project start date automatically export with constraints.

To keep task Start Dates from changing to the project Start Date in the MSP New Driver, the solution would be to add one of the following to the task:

1. A task constraint (See steps below)
2. A dependency to other tasks
3. Another other option is changing the % Complete value of the task to be greater than 0% (IE 1%). If the task has a % Complete value of greater than 0, this will add an Actual Start date for the task, so when the task is exported to MSP, the Start Date is pulled from that Actual Start Date

To add a constraint to a task from within PPM:
Note: "Start no Earlier Than" or "Must Start On" constraints work best to resolve this issue as other constraints such as "Start No Later Than" can still change the task Start Date to the project start date. Example: If your project start date is 05/01/2018, and the Task Start date is 05/05/2018, adding a "Start No Earlier Than" constraint of 05/04/2018 will keep the task from exporting to MSP as the project start date of 05/01/2018. 

1. In PPM, go to Home->Projects then click on the link for the project.

2. Click on the Tasks tab.

3. Click on the link for the task.

4. Select the 'Properties' tab and then click 'Constraints'.

5. Populate a date in one of the Constraints fields based on how you want the task to behave, then click Save and Return.

Constraints can also be added in MSP:

1. Export the project from PPM to MSP.

2. Double click on the task and click on the 'Advanced' tab.

3. Add a Constraint type (other then As Soon As Possible) and Constraint date and click OK.


  • To update multiple tasks, you can instead add the Constraint Type and Constraint Date to your Task/Gantt view in MSP and update the fields from the column. 
  • Other factors can impact dates being exported including
    • The Actual Start date of the task, which can override constraints set. Once the % Complete of a task is higher than 0%, this will populate the Actual Start Date which drives the Task Start Date.
    • Another factor is non working days or Holidays set on the PPM calendar. This also can cause task Start/Finish dates to be pushed out.
Additional Information:

Click here to view information on this change, as well as other differences between the MSP Legacy and MSP New driver from the PPM Project Management User Guide
Reference KB000098871 - MSP: Task Finish Dates are being pushed out when opening a project from PPM to MSP due to an issue with allocation
Reference TEC1606998 : In the MSP New driver, highlighting of tasks is no longer saved
Reference TEC1545414 : In the new MSP Driver, custom views are not Saved
Reference KB000071385 - CA PPM and MSP integration - List of Knowledge Documents
Reference KB000015956 - CA PPM and MSP integration known defects - Support Technical Document Index