Baseline Work on Timesheet View

[JodyJ]

In PWA, I added the field "Baseline Work" to the timesheet view so that
resources would be able to see what the original baseline was for a task.

I've created a project plan and baselined it but this field does not
populate. Any idea why?

 

[Dale Howard [MVP]]

JodyJ --

Refer to the following FAQ:

http://www.projectserverexperts.com/Shared Documents/changetimesheet.htm

Hope this helps.

 

[Bart]

Hi,
you have to add Baseline work in the Published fields of the projects that
you are publmishing.

Tools/customize/published fields

Bart

 

[Amy]

Hi Dale,

I have successfully added the baseline to the timesheet for a new project.
Is there a way to do this for projects that are in process?

Amy

 

[Dale Howard [MVP]]

Amy --

The managers of each other project would need to complete the same set of
steps you followed, as specified in the project managers section of the
following FAQ:

http://www.projectserverexperts.com/Shared Documents/changetimesheet.htm

Hope this helps.

 

[Amy]

I have followed the same steps for new and existing projects and it is only
working for projects being added to the server for the first time. Is there
some admin settings that I need to adjust?

 

[Dale Howard [MVP]]

Amy --

Are you absolutely certain that your project managers have added the
Baseline Work field to each existing project using Tools - Customize -
Published Fields, and then they have republished the assignments in each
existing project using Collaborate - Publish - Republish Assignments? If
not, they all MUST do this for every existing project. Let us know.

 

[Amy]

I found the error. When defining the fileds to publish to the enterprise I
had the 'task' rather than 'assignment' custom filed type radio button.
After this change everthing worked fine.

Could you provide some detail on functionality of these two options?

 

[Dale Howard [MVP]]

Amy --

We do not recommend using the Task option when pushing either the Actual
Start or Actual Finish fields to the PWA timesheet. If you push the Task
version of either field to the timesheet, the last person who enters an
Actual Start or Actual Finish value will determine the values for the entire
task. Consider this:

1. You have three resources (Mickey, Butch, and Pancho) assigned to Task A,
which is scheduled to start December 19.
2. You push the task version of the Actual Start and Actual Finish fields
to each user's timesheet.
3. On 12/19, Mickey enters an Actual Start date of 12/19.
4. On 12/20, Butch enters an Actual Start date of 12/20.
5. On 12/21, Pancho enters an Actual Start date of 12/21.

Because you pushed the task version of the Actual Start date field to each
user's timesheet, the system determines the Actual Start date of the task to
be 12/21, which is totally incorrect. You see? The last person who submits
an update on the task controls the Actual Start date or the Actual Finish
date for the task.

On the other hand, given the same scenario as above, if you push the
Assignment version of the Actual Start and Actual Finish fields to each
user's timesheet, then the system would determine that the Actual Start date
of the task is 12/19, because that is the earliest assignment Actual Start
date. Whichever resource finishes their work last and enters their Actual
Finish date will determine the Actual Finish date for the task, since the
latest assignment Actual Finish date will determine the Actual Finish date
for the entire task.

Hope this helps. Also, thanks for perservering until you found the
solution. And thanks for sharing the solution to your problem with us.