Migration: Migrated custom fields can't sync with plan

[GM]

We migrated a set of enterprise global fields from 2003 to 2007. However,
some of the post migration changes to these fields can't be reflected into
project professional for all plans.

Example, we have a project outline code in 2003 called Portfolio, which is a
hierarchical set of values. In 2003, we allowed selection of non-leave node
and didn't allow multi-selection. After migration, we changed the settings of
the field to allow only leave node and multi-selection. However, these
changes are neither picked up by migrated project plans nor newly created
project plan.

If we create a new custom field pointing to the same lookup table, then the
changes will be reflected in the project plan.

Any advice? Please.

Thansk in advance.

GM

 

[Andrew Lavinsky]

Have you tried clearing the cache for some of the computers running the plans
in question? That is the first thing to check when you see mixed up lookup
tables and fields.