Forum Discussion
Project for the Web - % complete calc error
Hi, it appears that be the order in which the effort/duration etc. fields are entered/edited, changes the calculation from % of effort completed to a % of time elapsed.
When entering a new task, typically I enter those details in the order:
Task name
Start
Finish
(accept the calculated duration)
Assign a resource
Effort (overwriting the calculated effort - typically my resources will only work part-time on project work e.g. 4 days of effort may require 4 weeks duration)
Effort completed (amend as needed)
Effort remaining (accept the calculated value)
% complete (accept the calculated value)
..this works fine - regardless of the start/finish (calculated duration), if I set:
effort of 100 days
update effort completed to 50 days
effort remaining will be 50 days
% complete will be 50%
However, if I then change the start or finish date – at this point the % complete calc changes to an unknown calculation which is neither % of effort or elapsed time. Even when putting the fields back to their original values, % complete doesn’t return to original value?!
3 Replies
I tried reproducing the error as you described, but the calculations, while odd at times were correct. My example was a single task with one resource assigned and no dependencies or constraints.
In your example assuming you have dependencies, check the task Dependency Type, Delay Type and ensure you no task constraints set as all of these can impact the calculations.
Also, in your example you mentioned you could % values didn't return to the original value even when setting all the values back to original. This is possible depending on the amount of change you made.
More details would help and as previously mentioned the order in which the changes are made can impact the calculations.If you give a more precise example JBateman and HannahM89 with full details of the changes made I should be able to explain what is happening and why it is giving the result it is. In my experience the calculations are usually 'correct' but the logic for the correct values isn't always obvious and may not look 'right'. Behind the scenes Project for the web uses the same scheduling engine as the Project desktop application - so tried and trusted for many years, but the more minimal UI in Project for the web sometimes means that there are some assumptions made that can catch you out. Certainly the order of operation is very important to what those assumptions might be.
Brian
I'm also having issues with the % compete not calculating correcting. Is there any solution to this?
