H
hc
Hello!
I configured PJS 2007 with different custom fields at project level, with
look-up tables. All look-up tables have also these two values: "not specifed"
and "not applicable". Everything worked very fine to our customer, but
suddenly I discovered that some look-up table doesn't have the value "not
applicable" anylonger. Instead, this value was randomly replaced with "
blocked" or "on schedule" or "rejected" or "early" or proposed" or
"completed" or "approved" or "late". This is for some fields not for all of
them.
This is happening only in Project Pro! The same fields, in PWA show the
correct value "not available".
Also, if you select lets say "blocked" and save and publish the project, in
Project Center you will see "not applicable" for that project. Only in
Project Pro, the field shows "blocked" instead of "not applicable".
Have any of you encountered this problem? Looking forward for any possible
advise!
Thank you!
Hilde
--
I configured PJS 2007 with different custom fields at project level, with
look-up tables. All look-up tables have also these two values: "not specifed"
and "not applicable". Everything worked very fine to our customer, but
suddenly I discovered that some look-up table doesn't have the value "not
applicable" anylonger. Instead, this value was randomly replaced with "
blocked" or "on schedule" or "rejected" or "early" or proposed" or
"completed" or "approved" or "late". This is for some fields not for all of
them.
This is happening only in Project Pro! The same fields, in PWA show the
correct value "not available".
Also, if you select lets say "blocked" and save and publish the project, in
Project Center you will see "not applicable" for that project. Only in
Project Pro, the field shows "blocked" instead of "not applicable".
Have any of you encountered this problem? Looking forward for any possible
advise!
Thank you!
Hilde
--