M
Mike
In our Project Server 2007 environment (SP1 only), we're starting to
have issues with our lookup tables. When either creating a new lookup
table, adding new options to existing tables, or modifying existing
values, the entered value is being changed to a "1". Also, we are
unable to indent/outdent lookup tables. What's interesting is that
we're still able to use custom fields with lookup tables just fine (in
Proj Pro or PWA) and the selected values are being pushed to the
Reporting Database. So it seems our only problem is maintining lookup
tables.
I have saved one lookup table after seeing this issue (thinking it's
only a display problem). Unfortunately, after saving, all values in
that lookup table were promptly deleted. Lucky for me, it was a new
lookup table that wasn't being used yet.
I did take the 4 Project Server databases and created a new instance
in a VPC environment and sure enough, I can maintain lookup tables as
expected and all the values exist just fine (indent/outdent, add new,
etc.. no problem). So, I'm not sure that the issue is with the
Project Server databases/tables.
We're also getting ready to install the Infrastructure Update but I'd
like to see this resolved before we do that. Frankly, I'm reluctant
to do much to the environment without getting a clear understanding to
what this problem is and seeing it fixed.
Has anyone seen this before and/or is there a resolution?
Thanks!
-- Mike
have issues with our lookup tables. When either creating a new lookup
table, adding new options to existing tables, or modifying existing
values, the entered value is being changed to a "1". Also, we are
unable to indent/outdent lookup tables. What's interesting is that
we're still able to use custom fields with lookup tables just fine (in
Proj Pro or PWA) and the selected values are being pushed to the
Reporting Database. So it seems our only problem is maintining lookup
tables.
I have saved one lookup table after seeing this issue (thinking it's
only a display problem). Unfortunately, after saving, all values in
that lookup table were promptly deleted. Lucky for me, it was a new
lookup table that wasn't being used yet.
I did take the 4 Project Server databases and created a new instance
in a VPC environment and sure enough, I can maintain lookup tables as
expected and all the values exist just fine (indent/outdent, add new,
etc.. no problem). So, I'm not sure that the issue is with the
Project Server databases/tables.
We're also getting ready to install the Infrastructure Update but I'd
like to see this resolved before we do that. Frankly, I'm reluctant
to do much to the environment without getting a clear understanding to
what this problem is and seeing it fixed.
Has anyone seen this before and/or is there a resolution?
Thanks!
-- Mike