search cancel

MSP: Partial durations are rounded up to the nearest whole numbers for Fixed Duration Tasks


Article ID: 130639


Updated On:


Clarity PPM SaaS Clarity PPM On Premise


In the Microsoft Project (MSP) New Driver, partial durations are rounded up to the nearest whole numbers for Fixed Duration Tasks that are less than 1 day when you save a project to PPM then open in MSP. Example: if the duration of a task is .3 days, when you save it to PPM and export it back to MSP, it changes to 1 day. This doesn't happen for Fixed Units tasks or tasks greater then 1 day (IE 1.3 days). 


1. Create a new project in Clarity PPM (No tasks or team members) 
2. Export the project to MSP using the MSP New Driver 
3. In MSP, create one auto scheduled task with task type of Fixed Duration 
4. Change the duration to .3 days 
5. Save the project back to PPM 
(Note that the task duration is correct in PPM displaying .3 days) 
6. Open the project again in MSP and review the task duration 
Expected Results: The task duration displays as .3 days 
Actual results: The task duration changes to 1 day 

Note: Summary tasks will see this issue at higher durations then 1 days as it's taking the totals of the partial duration tasks beneath it. So, if the summary task has 5 partial days at .1 days, .2 days, .3 days, .5 days, .3 days beneath it, and this adds up to the summary task duration of 1.4 days based on start/finish dates of the tasks and dependency relationships beneath it, when those tasks round up to 1 day each, the summary task changes to 5 days of duration.


Release: CODFSS99000-15.5-PPM SAAS FedRAMP-Sandbox-Small Environment


This issue is current under review as DE48524.