F
Francisco Alcala
Hi everybody.
I found a strange behavior in Project Server 2003. I don't know what am I
doing wrong:
- I need to track both % Work Complete and Physical % Complete in my
Projects. I created some Enterprise templates, and at the
"Tools>Customize>Published fields" I tried to add the "Physical % Complete"
to the published fields. I also tried to allow resources to change this
field, with a warning saying that this field has no assignment value, so the
resource will affect the task value of the field. This could be a nuisance
with tasks that have more than one resource, but anyway I can live with that.
No problem so far.
- Then I modified the Timesheet view in Web Access. I tried to add the
"Physical % Complete" field to the timesheet, in order to have the resources
to see and modify the field, but this field is not in the list of fields!!!
So, the resources can register their work but not the Physical % Complete of
the task.
- More puzzling: the field DOES appear at the Updates page in web access,
when the Project Manager reviews the reported work. Of course, the value of
the field is 0% (or whatever the value of the field is)...
As a solution, I created a custom numeric task field. This can be also
published but in this case the field can be modified at assignment level.
However, the solution is not ideal because:
- even when the resource can change the value of the field of his/her
assignment instead of the task value, there is no summary or rollup for these
values, so the field in a tasks view still shows a value of 0.
- I changed the published field so the resources can modify the TASK value
instead of the assignment value. At this time, the summary and rollup worked,
but the field is still a numeric field. Resources can report a value of more
than 100, or negative. Project Managers can still filter these values but
errors can occur.
- The Physical % Complete field is still 0%; if I want to calculate Earned
Value based on this field, I will need to create a macro for assigning values
to this field.
Seems like a bug to me. Other fields (like cost values) work as expected.
Any ideas?
Thanks in advance.
I found a strange behavior in Project Server 2003. I don't know what am I
doing wrong:
- I need to track both % Work Complete and Physical % Complete in my
Projects. I created some Enterprise templates, and at the
"Tools>Customize>Published fields" I tried to add the "Physical % Complete"
to the published fields. I also tried to allow resources to change this
field, with a warning saying that this field has no assignment value, so the
resource will affect the task value of the field. This could be a nuisance
with tasks that have more than one resource, but anyway I can live with that.
No problem so far.
- Then I modified the Timesheet view in Web Access. I tried to add the
"Physical % Complete" field to the timesheet, in order to have the resources
to see and modify the field, but this field is not in the list of fields!!!
So, the resources can register their work but not the Physical % Complete of
the task.
- More puzzling: the field DOES appear at the Updates page in web access,
when the Project Manager reviews the reported work. Of course, the value of
the field is 0% (or whatever the value of the field is)...
As a solution, I created a custom numeric task field. This can be also
published but in this case the field can be modified at assignment level.
However, the solution is not ideal because:
- even when the resource can change the value of the field of his/her
assignment instead of the task value, there is no summary or rollup for these
values, so the field in a tasks view still shows a value of 0.
- I changed the published field so the resources can modify the TASK value
instead of the assignment value. At this time, the summary and rollup worked,
but the field is still a numeric field. Resources can report a value of more
than 100, or negative. Project Managers can still filter these values but
errors can occur.
- The Physical % Complete field is still 0%; if I want to calculate Earned
Value based on this field, I will need to create a macro for assigning values
to this field.
Seems like a bug to me. Other fields (like cost values) work as expected.
Any ideas?
Thanks in advance.