G
Greg Horodeck
In practice migrations of our migration from Project Server 2002 to 2003 we
have encountered a situation where all of the resources on projects migrate
over as proposed rather than committed. Also, many but not all of the
resources migrate over in the resource pool with a defualt of proposed.
Interestingly enough, immediately after the migration, the projects appear
on their timesheets until the PM publishes, then they disappear,obeying the
proposed status.
With 6,400 projects, having the PM's go in and change all of their resources
to committed and republish is out of the question.
We have tried updating the database directly through SQL but some of the
information necessary is stored in blobs that we cannot address.
Has anyone encountered this situation and have a solution?
Greg
have encountered a situation where all of the resources on projects migrate
over as proposed rather than committed. Also, many but not all of the
resources migrate over in the resource pool with a defualt of proposed.
Interestingly enough, immediately after the migration, the projects appear
on their timesheets until the PM publishes, then they disappear,obeying the
proposed status.
With 6,400 projects, having the PM's go in and change all of their resources
to committed and republish is out of the question.
We have tried updating the database directly through SQL but some of the
information necessary is stored in blobs that we cannot address.
Has anyone encountered this situation and have a solution?
Greg