Custom Fields in Project 2010
Applies to: Office 2010 | Project 2010 | Project Server 2010 | SharePoint Server 2010
Custom fields extend the attributes of tasks, resources, or projects in Microsoft Project 2010. You can filter, group, sort, and create OLAP cubes and reports based on custom field values. Project 2010 extends the functionality and ease of use of custom fields compared to previous versions of Project.
Following are the main improvements for custom fields in Microsoft Project Server 2010:
Custom field collections can be associated with the name of a department. You can programmatically define departments in the Department lookup table using the CreateLookupTables, UpdateLookupTables, or UpdateLookupTablesMultiLang methods. You can also use the Enterprise Custom Fields and Lookup Tables page in Project Web App (https://ServerName/ProjectServerName/_layouts/PWA/Admin/CustomizeFields.aspx)
Microsoft Project Professional 2010 enables access to all custom fields, although it can filter custom field lists based on the project or resource department. Project Web App can restrict users outside of a department from editing custom fields; however, the Project Server Interface (PSI) enables users to edit custom fields in department collections that are owned by other departments.
Project Web App stores dates in a standard internal format that is independent of locale settings.
CustomFields class methods for creating, reading, and updating enterprise custom fields each include a matching method that handles locale-dependent formulas. For example, the ReadCustomFields method ignores the locale format for formulas and the ReadCustomFields2 method returns a CustomFieldDataSet that has formulas in the locale format.
It is not necessary to launch Project Professional 2010 to create or validate custom field formulas.
Custom field formulas are calculated on a server-side publish operation.
Graphical indicators are updated after changing the value in Project Web App.
Cost custom fields that are based on a formula work properly in Project Server 2010.
You can use semicolons (;) in server-side formulas, even when a semicolon is the defined list separator in regional settings.
If one custom field formula fails to evaluate for an entity, the remaining custom field formulas continue to evaluate.
Project Server 2010 includes default lookup tables and custom fields for portfolio analysis. Lookup tables include Primary Objective and Areas Impacted. Custom fields include Compliance Proposal, Proposal Cost, Project Departments, Post Implementation Review Date, Areas Impacted, Primary Objectives, Business Need, Goals, and Assumptions. Default custom fields also include proposed and approved start and finish dates.
Custom field behavior can be controlled by a Project Server workflow. For example, a workflow can make a custom field read-only or required at a stage level.
Timesheet custom fields are added to the Reporting database.
Text custom fields can be multiline up to 4000 bytes, for use in project detail pages (PDPs) and with workflows for demand management in Project Web App. Multiline text custom fields are not usable in Project Professional.
In This Section
Local and Enterprise Custom Fields
Creating Lookup Tables and Enterprise Custom Fields
Rollup and Roll-Down Custom Fields
Using Formulas and Graphical Indicators with Custom Fields
Custom Fields and the Reporting Database