Disappearing values in custom fields

[Bill Mc]

I've encountered a bizarre problem. I have an existing project with local
custom fields that i am loading into Project Server 2007. These are standard
Text fields with local lookup tables for the values. I save the project in
the draft database and then publish it. Later when I go to open the draft
version in Project 2007, the values in the custom fields are blank and the
lookup tables are even gone. Even more bizarre, I open the published
version, which should be identical and the values for the custom fields are
populated in that version. I've run several tests with this and some times
the custom fields are populated, sometimes they are blank. Nothing
consistent however in my testing.

Are there any pitfalls with regards to local custom fields that i should be
aware of when loading projects into Project Server? We may at some point
incorporate some of these local custom fields into the enterprise but thought
they would work as local for the time being.

 

[Dale Howard [MVP]]

Bill --

I have also run into problems with custom fields containing a Lookup Table,
including cross

 

[Dale Howard [MVP]]

Bill --

Like you, I have also run into problems with custom fields containing Lookup
Tables, including cross-Lookup Table pollution. For example, when I open
the Enterprise Resoruce Pool for editing, the RBS field shows values for
only a few resources, in spite of the fact that I populated an RBS value for
everyone. I suspect problems such as yours and mine are some of the bugs
that Microsoft must fix in SP1. Hope this helps.

 

[Sinek]

Did yout try to delete local cache?

Bill --

Like you, I have also run into problems with custom fields containing
Lookup Tables, including cross-Lookup Table pollution. For example, when
I open the Enterprise Resoruce Pool for editing, the RBS field shows
values for only a few resources, in spite of the fact that I populated an
RBS value for everyone. I suspect problems such as yours and mine are
some of the bugs that Microsoft must fix in SP1. Hope this helps.

 

[Dale Howard [MVP]]

Yes, and it did not help. That is a workaround to this issue, but it
apparently does not work for everyone. Thanks for asking!

 

[Bill Mc]

Dale,

What is this workaround that you speak of? It seems to me that if valuable
data is disappearing from these fields then this could be a problem that
prevents us from using Project Server in a production environment. Do you
know if MS is aware of this problem, as I haven't seen anyone else mention it
on the net.

Thanks,
Bill
--
Bill McGrath PMP

Yes, and it did not help. That is a workaround to this issue, but it
apparently does not work for everyone. Thanks for asking!

 

[Vadim Gerya]

Hi All !
We start production enviroment and everything blow up due to lossing
bussines critical data in project local fields. I have spent about 60 hours
trying to understand what is exactly going on with local custom field data
dissapearing. Unfortunalty, No reasonable workaround found yet ...
I suppose sometimes MS Project Pro 2007 does not correctly read (or display)
data from database. Obviosely it is connected with new impemetation of data
exchange algorithm beetween DB and MS Project Pro (using SOAP protocol, local
cache impementation and so on).
When I open project from enterprise (from local cache or after clearing one)
in 1 case of 10 Project 2007 Pro displays local field incorrectly. For
example: you save, publish and close (check in) project then open it and you
may discover that all Text, Number, Flag, Cost and other local fields have
been occsionally assigned to lookup tables (wich are not exist). But data in
DB is correct!!.
If project has more than 1500 tasks - you may find this bug 2 times on 5
openings.

If I found workaround or something new, I post it ....

 

[Gary L. Chefetz [MVP]]

Vadim:

Try deleting the local cache files

appdata\microsoft\project 2007\ clear the two files below this.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[mike.mahoney]

Vadim:

Try deleting the local cache files

appdata\microsoft\project 2007\ clear the two files below this.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting:http://www.msprojectexperts.com
For Project Server FAQS:http://www.projectserverexperts.com








- Show quoted text -

Vadim

I will share my experience. Prior to implementing 2007 I set up MSP
2003 plans with local custom fields (pick lists / indicators) to bring
plans to the "right level" and to get users familiar with planning
processes. The intent was to replace these local custom fields with
enteprise equivalents. The desktops were converted to MSP 2007 and
plans saved to 2007 mpp files. Once the PS 2007 was configured I
migrated these plans into the new server. The migration came up with
two principle issues: a number of assignments were not acceptable to
projectserver they caused My task page to return with unexpected
error. This was resolved by identifying the problem assignment - a
slow painful process. The second problem was local custom fields. At
first sight they looked fine but as they had been replaced with
enterprise fields my intent was to delete them via the organiser.
However after doing this and on reopening the organiser the fields
"returned" with system names rather than custom names. Essentially
they could not be deleted. On looking at the data in these field
instead of containing text many contained symbols. So clearly there
is a problem with local custom fields particularly after migration.
Whether you can succesfully set them up post migration I don't know (I
am avoiding the issue). The only method I could use to sort out the
corrupted plans was to save them to Project Excel template format and
reimport using the same wizard, effectively clearing out custom data.
Again a slow painful process.

regards

Mike

 

[ahelp]

I hope SP1 is coming soon! We have two custom required fields using the RBS
as a lookiup table. The values not only did not migrate properly, but only
two options out of an RBS of ~300 are available from which to choose. In the
RBS field itself, the whole list is available. Deleting everything in the
cache folder had no effect. Any word on when SP1 might be out?
Thanks,
Mike

 

[Dale Howard [MVP]]

Mike --

No word yet. You'll know when we know. Microsoft has released the first
hotfix at:

http://support.microsoft.com/kb/935557

It fixes one small but very annoying bug with the Import Projects wizard.
I'll bet many more will be tricking out before the SP arrives.

 

[ahelp]

Thank you, we were just wondering about hotfixes...

 

[Vadim Gerya]

Does not work .. unfortunately.