M
MG
I have several times been experiencing that Microsoft Project moves
Actuals to other time periods than those where they were originally
entered. I know this can happen if you for instance manually set a
Finish Date on a task that is before the last Actual on that task,
however then Microsoft Project gives a warning and a chance to undo.
I am absolutely sure that MS Project has moved Actuals several times,
without me having touched the Finish Date, and without giving me any
warning. Can anyone please explain to me what can cause this to
happen, so I can try avoiding it?
I know I can synchronize with protected actuals, however that deletes
any timesheet entries made by people that have not yet been submitted
for approval, so it is not a great solution.
Actuals to other time periods than those where they were originally
entered. I know this can happen if you for instance manually set a
Finish Date on a task that is before the last Actual on that task,
however then Microsoft Project gives a warning and a chance to undo.
I am absolutely sure that MS Project has moved Actuals several times,
without me having touched the Finish Date, and without giving me any
warning. Can anyone please explain to me what can cause this to
happen, so I can try avoiding it?
I know I can synchronize with protected actuals, however that deletes
any timesheet entries made by people that have not yet been submitted
for approval, so it is not a great solution.