none
Deleting custom fields in Project Server 2007 - any dangers to look out for? RRS feed

  • Question

  • We've got several custom fields at the project level that will probably never be used.  I need to clean things up a bit to make things less cluttered to the user.  Any problem with zapping these if I know they won't be used moving forward, considering projects in the archive database, etc.?

    Thanks,
    Andy Novak, PMP, MBA
    University of North Texas

    Monday, May 2, 2011 9:46 PM

Answers

  • Andy --

    One of the issues I see occasionally at client sites is that the client has created way too many custom enterprise Project fields, and has made lots of them Required fields as well.  This places a burden on every PM when he/she creates a new project and has to fill in so many Project fields.  So, I commend you for wanting to make things less cluttered for your users.

    To answer your question, I cannot see any real problems with deleting custom enterprise fields that are no longer needed.  Just to be on the safe side, however, if it were me I would back up my custom enterprise fields and lookup tables, and then back up both the Enterprise Resource Pool and every enterprise project.  Only after that would I delete the custom fields that are no longer needed.  Hope this helps.


    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Tuesday, May 3, 2011 1:01 PM
    Moderator

All replies

  • Andy --

    One of the issues I see occasionally at client sites is that the client has created way too many custom enterprise Project fields, and has made lots of them Required fields as well.  This places a burden on every PM when he/she creates a new project and has to fill in so many Project fields.  So, I commend you for wanting to make things less cluttered for your users.

    To answer your question, I cannot see any real problems with deleting custom enterprise fields that are no longer needed.  Just to be on the safe side, however, if it were me I would back up my custom enterprise fields and lookup tables, and then back up both the Enterprise Resource Pool and every enterprise project.  Only after that would I delete the custom fields that are no longer needed.  Hope this helps.


    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Tuesday, May 3, 2011 1:01 PM
    Moderator
  • Andy --

    One additional thought about deleting custom enterprise fields.  If any field with a lookup table is included in the OLAP cube, I would remove the field from the OLAP cube before deleting it.  Hope this helps.


    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Tuesday, May 3, 2011 1:06 PM
    Moderator
  • Thank you Dale.    I'll carefully look at everything first and backup as you suggested before moving forward.

    Andy

    Tuesday, May 3, 2011 10:02 PM