Here is a quick naming convention tip for Microsoft Project Server 2007 and 2010 Enterprise Lookup Tables. To avoid any confusion when working with several Enterprise Custom Fields and Lookup Tables in Project Server, consider naming your Lookup Tables with the "Lookup" suffix:
Notice that I have not only named my new Lookup Tables with the "Lookup" suffix, but I have also renamed all of the built-in Lookup Tables as well:
To rename an existing enterprise lookup table, simply click on the Lookup Table name on the Custom Fields and Lookup Tables PWA page, edit the name on the Edit Lookup Table page, and save:
When you rename Enterprise Lookup Tables, notice that the Enterprise Custom Fields listing on the Custom Fields and Lookup Tables PWA page automatically updates to reflect the name changes as well:
The Lookup Table column in the Enterprise Custom Fields listing shows whether each Custom Field is using one of your configured Lookup Tables:
Some fields have no Lookup Table listed, either because they are manually-entered or calculated (as indicated in the Formula column).
An Added Reminder About Naming Enterprise Custom Fields and Lookup Tables
It has been said many times in our little community, but I cannot talk about naming Lookup Tables without also reminding you of a cardinal rule for naming Enterprise Custom Fields and Lookup Tables...
For your own sake (and sanity!)... ONLY use the following when naming these entities:
- Uppercase letters
- Lowercase letters
- Numbers
- Spaces
- Underscores
Do not EVER use special characters when naming Enterprise Custom Fields and Lookup Tables!
Good luck!