Identify and fix Enterprise Custom fields and Outline Codes with name conflicts (Project Server 2010)

 

Applies to: Project Server 2010

Topic Last Modified: 2010-05-05

There are certain custom fields and lookup tables name that are reserved in both Microsoft Office Project Server 2007 and Microsoft Project Server 2010. If any of these names are used in the current Project Server 2003 database, the custom fields and outline codes must be changed in Project Server 2003 before proceeding further with the migration. Use Microsoft Office Project Professional 2003 connected to a Project Server 2003 instance to look for reserved names, and take corrective action if necessary.

Reserved outline code names

Outline Code Name Type Office Project Server 2007 Project Server 2010

Cost Type

Resource

X

X

Health

Task

X

X

State

Project

X

X

Team Name

Resource

X

X

Department

X

Flag Status

X

Reserved custom field names

Custom field name Type Office Project Server 2007 Project Server 2010

Cost Type

Resource

X

X

Health

Task

X

X

State

Project

X

X

Team Name

Resource

X

X

Sample Approved Finish Date

Project

X

Sample Approved Start Data

Project

X

Sample Areas Impacted

Project

X

Sample Assumptions

Project

X

Sample Business Need

Project

X

Sample Compliance Proposal

Project

X

Flag Status

Task

X

Sample Goals

Project

X

Sample Post-Implementation Review Date

Project

X

Sample Post-Implementation Review Notes

Project

X

Sample Primary Objectives

Project

X

Project Departments

Project

X

Project Impact

Project

X

Sample Proposal Cost

Project

X

Sample Proposed Finish Date

Project

X

Sample Proposed Start Date

Project

X

Relative Importance

Project

X

Resource Departments

Resource

X