J
JodyJ
We've been using Project Server 2003 since the middle of July. We have
several instances (250 rows of data) in which people have entered time but it
never showed up in PWA for a PM to pull in to a project plan.
There was a previous post that discussed a hotfix
(http://support.microsoft.com/kb/893087) however, I've looked at this data
and there are many, many scenarios where the resource did not enter a zero on
their timesheet. If they did, they subsequentlly hit delete. With this many
errors, I'm guessing that this issue goes much further than deleting or
zeroing out a # but I can't find a pattern in the data.
Has anyone else had any success figuring out what the issue is? I'm in a
bit of a crunch here as the only way I have found to "fix" this is to go to
Adjust Actuals, change the hours that aren't updating, change them back to
the original hours and then click Update Actuals....obviously a very tedious
process and not likely to keep the same thing from happening going forward.
several instances (250 rows of data) in which people have entered time but it
never showed up in PWA for a PM to pull in to a project plan.
There was a previous post that discussed a hotfix
(http://support.microsoft.com/kb/893087) however, I've looked at this data
and there are many, many scenarios where the resource did not enter a zero on
their timesheet. If they did, they subsequentlly hit delete. With this many
errors, I'm guessing that this issue goes much further than deleting or
zeroing out a # but I can't find a pattern in the data.
Has anyone else had any success figuring out what the issue is? I'm in a
bit of a crunch here as the only way I have found to "fix" this is to go to
Adjust Actuals, change the hours that aren't updating, change them back to
the original hours and then click Update Actuals....obviously a very tedious
process and not likely to keep the same thing from happening going forward.