enterprise fields blank after task update

P

PSSP2007

I am implementing a Project Server 2007 solution for a client and in
doing so I needed to create a custom field that contains text used to
indentify and filter different sets of tasks. I created the field
using the web access and populated the schedule using Projec Pro. At
first, there were no values in the My Tasks view. After doing some
research, I found that I needed to "Roll down, unless manually
specified" in the "Calculation for Assignment Rows" setting. After
doing this the values appeared in the My Tasks view. The problem I am
having is that after a task is updated, the custom field goes back to
being blank. The value is still there when I open up the file in
Project Pro.

Any ideas as to why the value blanks out in the web access view?
 
D

Dale Howard [MVP]

PSSP2007 --

I am only speculating, but I suspect this is one more unreported bug in
Project Server 2007. I suspect this is somewhat like the Health field,
which doesn't show up in the Microsoft Project 2007 plan, even if the team
members specifies a Health value. Again, I'm speculating, so if someone
knows definitively, I'd welcome the chance to be corrected. Hope this
helps.
 
V

Vadim Gerya, PMP

Hi All!
May be I am wrong but ...

When you create task custom field and make it available in "My Task" view
please note that resource operate on assignment level when he/she enters data
in this field.
After accepting of task updates you may see entered data on task assignment
view in Project 2007 Pro. You do not see this data at task level. I write
VBA code to roll up data from assigment level to task level.
Plese note - I do not play with custom text task field but I have done this
for custom cost task field.

Hope this help :) !
 
D

Dale Howard [MVP]

Vadim --

You may very well be right in this case. I'm so tired of fighting the bugs
in Project Server 2007 that it's easy to declare every behavior as a bug and
not think seriously about what actual design features would cause certain
behaviors. Therefore, I sincerely apologize if I am wrong about this one.
 
V

Vadim Gerya, PMP

Ah Dale , ... the same for me.
I continue fighting trying to make this soft working stable and predictable
....

At present angry customers are hanging on my sholders cutting my head and I
also tend to see bugs all the time in any place...
 
P

PSSP2007

Ah Dale , ... the same for me.
I continue fighting trying to make this soft working stable and predictable
...

At present angry customers are hanging on my sholders cutting my head and I
also tend to see bugs all the time in any place...

--
Vadim Gerya, PMP








- Show quoted text
Click to expand...

Thanks for all your help!
 
R

ROS

Hi All,
I've ran to this situation as well were our users use custom fields to
quickly identify certain tasks. However, with the values from custom fields
disappearing after submitting task updates, the users are left to find
another way to locate their tasks. So, I believe the behaviour of the custom
fields maybe technically correct, but the functionality is not correct. From
the original post, the custom field is used for identification and filtering.
Users submit task updates on a weekly basis. Once they submit their task
updates, the ability to filter or identify tasks is no longer available for
the user. This filtering is very useful to the users, especially when they
are assigned to multiple tasks. Also, displaying data should be consistent.
If the value of the custom field is there to begin with, then value should
continue to display. Otherwise, this leads the user that the data
disappeared (or is missing).
 
Top