C
Clement
A few weeks ago, we were importing projects into Project
2003 Server. Most of these were ongoing projects with
progress data.
As soon as the projects were successfully imported, we
republished the assignments. Here is the catch: We did
not check the box "Overwrite Actual Work entered by
resources". The net effect of that is that the existing
Actual Work does not get transfered to "Protected Actual
Work". So when a resource sends a timesheet update to the
project manager, all updates entered in Project Web Access
by the resources overwrite any existing actual work.
Of course, we could re-start from the beginning and do it
right, but since then, our resources have created many
weeks of timesheets (that we don't want to update until
past actual work is protected).
My guess is that if I could find a way to copy Actual Work
(per task, per resource, per assignement, timescaled and
not) to "Actual Work Protected", I could then accept the
updates and I would preserve both Actual work from before
the import AND actual work from timesheets since the
import.
My problem is that these protected actual work fields are,
well, protected (read only). Is there a workaround to
writing data in these fields, probably a macro, or
something.
Thanks for your help
Clement
2003 Server. Most of these were ongoing projects with
progress data.
As soon as the projects were successfully imported, we
republished the assignments. Here is the catch: We did
not check the box "Overwrite Actual Work entered by
resources". The net effect of that is that the existing
Actual Work does not get transfered to "Protected Actual
Work". So when a resource sends a timesheet update to the
project manager, all updates entered in Project Web Access
by the resources overwrite any existing actual work.
Of course, we could re-start from the beginning and do it
right, but since then, our resources have created many
weeks of timesheets (that we don't want to update until
past actual work is protected).
My guess is that if I could find a way to copy Actual Work
(per task, per resource, per assignement, timescaled and
not) to "Actual Work Protected", I could then accept the
updates and I would preserve both Actual work from before
the import AND actual work from timesheets since the
import.
My problem is that these protected actual work fields are,
well, protected (read only). Is there a workaround to
writing data in these fields, probably a macro, or
something.
Thanks for your help
Clement