% Complete

[PK Consulting]

We have the following situation:

1 - We are SP2 on the clients, with whatever was before SP2A on the servers
2 - Our tasks are fixed duration, effort driven off, no constraints
3 - We use managed time frames.
4 - We experience two problems. First, we complete a task with no time
recorded against (via PWA) by removing the resources and updating the %
complete. After publishing, we sync with protected acutals and the %
completion values are set to zero. Second, we sometimes complete tasks with
time recorded against them (via PWA) by setting remaining duration to zero.
While this updates the % complete to 100%, we sometimes get the dreaded out
of sync message.

Any ideas?

PK Consulting

 

[Gary L. Chefetz [MVP]]

PK:

For your first scenario: When you remove a resource from a task, you should
first set the remaining work values for each resource to zero and then
publish new and changed assignments. After publishing the new zero value in
the assignment, then remove the resource from the task. I suspect what's
happening is that you're simply removing the resource without taking care of
the assignment values first.

I'm not sure what you're describing in scenario two, as "remaining work" is
what resources can adjust in a managed time period system. Is this what you
meant? Can you give a good example and include more of the task history?

As an aside, it certainly sounds as though Fixed-Duration planning is not
right for your situation. I suspect that your second issue is related to the
fact that you're conflicted between duration based planning and effort based
tracking.