Project Professional 2010 with Project Server 2010 - Issue using local custom fields RRS feed

  • Question

  • A few of my PMO’s are facing challenges with local custom fields.

    PMO’s from each division use local custom fields in addition to enterprise custom fields.

    (Not all local fields can be converted to enterprise fields due to federal structure and also to keep a check on performance)

    Current Issue:

    1. PMO’s create text based (no lookup table, no formulae) local custom fields

    2. They populate data in those fields and save/publish/check-in plan

    3. When they re-open the plan the values are lost

    4. Also, the text based fields get converted to lookup table based fields with no values in the lookup table

    Please let me if there is any potential workaround to get this resolved. Appreciate your response.

    Environment – Project Professional 2010 with Project Server 2010. Both client and server have April 2012 CU applied.



    Thursday, October 18, 2012 6:23 PM

All replies

  • Hello Sunny

    Basically it is this.  Local resources and custom fields are not saved in project schedules, if they are part of a project server database.  Your options are

    1) create a custom field on project.  Perhaps, a generic text field.

    2) Use SharePoint list in project workspaces

    3) create excel documents and save in workspaces.


    Michael Wharton, MBA, PMP, MCT, MCSD, MCSE+I, MCDBA, MCC 2011, MCC2012
    Blog contains my field notes and SQL queries

    Friday, October 19, 2012 2:02 AM
  • Hello Sunny, just as Michael said you cannot save or publsih a local field. The following is from Microsoft.... 

    "To migrate a local custom field to an enterprise custom field, open the Custom Fields dialog box in Project Professional 2010 (on the Project tab of the ribbon, click Custom Fields). Select Task or Resource and the field type, click the local custom field you want to migrate, and then click Add Field to Enterprise. If you add a task or resource outline code as an enterprise custom field, it becomes an enterprise Text custom field with a hierarchical lookup table."

    and the link to the article is:

    Hope it helps

    Friday, October 19, 2012 9:10 AM
  • Thanks for your replies.

    I am using generic text based in my plans. These are task based fields and NOT PROJECT based fields.

    Michael - my users are doing what you have suggested in point one. However as mentioned in my problem statement the text based fields after save are converted to lookup tables.

    Manos SM - Local custom fields in a project plan can be saved and published. They are not passed on to the reporting database.

    My problem is similar to this post -

    Friday, October 19, 2012 1:16 PM
  • Hi Sunny,

    Did you find a solution to your problem? We are in the same situation where we have a custom LOCAL field with lookup values that disappear after saving in Project Server 2010. If values are assigned to the tasks, those do persist, but the lookup table values are gone, which are needed in case new tasks get added. 

    Please let me know if you found a resolution for this. 

    Thursday, February 21, 2013 7:33 PM
  • Unfortunately I dint find any solution. I advised my users to use local custom fields WITHOUT lookup tables.

    If it’s extremely necessary we create enterprise field with lookup tables as they persist.

    Thursday, February 21, 2013 9:14 PM