ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

In the MSP New Driver, Constraints for External Dependencies are not exporting to MSP


Article ID: 7139


Updated On:


Clarity PPM SaaS Clarity PPM On Premise


Constraints set for external dependencies aren’t exported in the Microsoft Project (MSP) new driver, which can then cause dates of tasks to change. Example, if you set a “Must Start On” constraint on a task, when you export a project that has a task linked to it as an external dependency, it exports the constraint type incorrectly as “As Soon as Possible” instead of “Must Start On”.

1. Create two new projects with one task each 
2. Navigate to the Task on the first project 
3. Create a Must Start On Constraint of 6/10/17 
4. Click on the Properties tab for the task and select 'Dependencies' from the drop down 
5. Click 'New' 
6. Click the Browse icon next to Project to search for the second project created, select the project and click 'Add' 
7. Click Filter, select the task created in the second project, and click Next then 'Save and Return' 
8. Export the second project created to MSP and add the Constraint Type and Constraint Date columns to the view 

Expected Results: For the task that is an external dependency for the project, Constraint Type shows "Must Start On' and 'Constraint Date' shows 6/10/17 
Actual Results: Constraint Type shows 'As Soon as Possible' and 'Constraint Date': NA 


This issue is caused by DE34102


This issue applies to the MSP New Driver for CA PPM 14.4, 15.1, and 15.2


This issue is fixed in CA PPM 15.3.

Additional Information

Reference the Customer Reported Defect Resolution Policy for CA PPM