Task Custom Fields PS2007 - My Assignments

M

Mike

I am investigating the demo database for PS2007.
There is a task custom field called "Health". The field appears in My
Assignments view and can be updated there. On my system the update
does not make it to the MSP plan. On further investigation any
changes made directly in the MSP plan to this field are not sustained,
and in turn are not published to the assignment view. Possibly a
corruption in the database.

I created another task custom pick list, which I can update in MSP but
when I try to add it to my assignments view it is not offered in the
list of available fields.

In 2003 you enabled additional fields in the timesheet by defining
"published fields".

Q1: Does anyone else see this behaviour?
Q2: Is there a step I am missing to make a custom field available to
assignment/timesheet views?

Thanks

Mike
 
M

Mike

I am investigating the demo database for PS2007.
There is a task custom field called "Health". The field appears in My
Assignments view and can be updated there. On my system the update
does not make it to the MSP plan. On further investigation any
changes made directly in the MSP plan to this field are not sustained,
and in turn are not published to the assignment view. Possibly a
corruption in the database.

I created another task custom pick list, which I can update in MSP but
when I try to add it to my assignments view it is not offered in the
list of available fields.

In 2003 you enabled additional fields in the timesheet by defining
"published fields".

Q1: Does anyone else see this behaviour?
Q2: Is there a step I am missing to make a custom field available to
assignment/timesheet views?

Thanks

Mike
Click to expand...

Follow up:
The demo system has a "blank database". In this however there are
still a number of predefined custom fields, including health. In this
environment I could define additional custom task fields and display
them in My Assignments, but could not change and return values to
MSP.
A further problem occurred with one of the fields "cross-linking" with
the health field. The drop down for the health field had a mix of the
health pick list and some from my new custom field. I noticed this
problem previously in the beta2 release. I have yet to investigate in
a new build situation but it is a cause for concern.

regards

Mike
 
D

Dale Howard [MVP]

Mike --

To answer your questions:

Q1: Yes, I see the same behavior as you.
Q2: Like you, I too am unable to add a custom enterprise Task field to
either the My Assignments view or the Details (Assignment Details page)
view.

Because Project Server 2007 is pre-SP1, I think this behavior is part of the
"rough around the edges" nature of the software. Hope this helps.
 
D

Dale Howard [MVP]

Mike --

Project Server 2007 includes five built-in custom fields. These fields are:

Cost Type (includes the Cost Type lookup table)
Health (includes the Health lookup table)
RBS (includes the RBS lookup table)
State (includes the State lookup table)
Team Name (SHOULD include the Teams lookup table, but DOES NOT)

A first step for the Project Server 2007 administrator should be to create a
Teams lookup table, populate it with the names of teams in his/her
organization, and then include the Teams lookup table in the Team Name
field.

Regarding your second point about the "cross linking" behavior you have
seen: I have seen it as well. This behavior seems to be sporadic and
inconsistent from user to user with custom fields added to the blank
database. For example, I created a custom enterprise Project field attached
to a custom Lookup Table. Using the Farmadmin account, I don't see the
"cross linking" behavior. Logging in as a user who is a member of only the
Project Managers group, I see the "cross linking" behavior between fields.
Again, as I stated in my previous post, I think this is part of the "rough
around the edges" behavior of a pre-SP1 software system.

Hope this helps.
 
M

Mike

Mike --

Project Server 2007 includes five built-in custom fields. These fields are:

Cost Type (includes the Cost Type lookup table)
Health (includes the Health lookup table)
RBS (includes the RBS lookup table)
State (includes the State lookup table)
Team Name (SHOULD include the Teams lookup table, but DOES NOT)

A first step for the Project Server 2007 administrator should be to create a
Teams lookup table, populate it with the names of teams in his/her
organization, and then include the Teams lookup table in the Team Name
field.

Regarding your second point about the "cross linking" behavior you have
seen: I have seen it as well. This behavior seems to be sporadic and
inconsistent from user to user with custom fields added to the blank
database. For example, I created a custom enterprise Project field attached
to a custom Lookup Table. Using the Farmadmin account, I don't see the
"cross linking" behavior. Logging in as a user who is a member of only the
Project Managers group, I see the "cross linking" behavior between fields.
Again, as I stated in my previous post, I think this is part of the "rough
around the edges" behavior of a pre-SP1 software system.

Hope this helps.

--
Dale A. Howard [MVP]
Enterprise Project Trainer/Consultanthttp://www.msprojectexperts.comhttp://www.projectserverexperts.com
"We wrote the book on Project Server"






- Show quoted text -
Click to expand...

Thanks Dale

The in-built fields presumably support functionality or process. I
understand RBS, Team and State (though not seen its result) but what
are cost type and health driving/supporting?

When can we expect SP1?

regards


Mike
 
D

Dale Howard [MVP]

Mike --

I believe that Cost Type drives reporting on financial information. I think
Health is up to you on how you want to use it. I have no idea about SP1. I
don't work for Microsoft and have no insider knowledge. Hope this helps.
 
Top