CustomFields.CreateCustomFields2 method

Office 2013 and later

Creates enterprise custom fields, where formulas are in a language-dependent format.

Namespace:  WebSvcCustomFields
Assembly:  ProjectServerServices (in ProjectServerServices.dll)

[SoapDocumentMethodAttribute("", RequestNamespace = "", 
	ResponseNamespace = "", 
	Use = SoapBindingUse.Literal, ParameterStyle = SoapParameterStyle.Wrapped)]
public void CreateCustomFields2(
	CustomFieldDataSet cfds,
	bool validateOnly,
	bool autoCheckIn


Type: WebSvcCustomFields.CustomFieldDataSet

The CustomFieldDataSet contains the custom field definitions.

Type: System.Boolean

If true, validate the CustomFieldDataSet without creating the custom fields.

Type: System.Boolean

If true, check in the custom fields after they are created.

Formulas in the CustomFieldDataSet that are used to calculate custom fields or graphical indicators can be written in the locale format that is specified in the Regional and Language Options control panel of the computer running Project Server. The CreateCustomFields2 method saves the formulas in a language-independent format. By comparison, the CreateCustomFields method saves formulas without regard to the locale format.

Caution noteCaution

The CreateCustomFields method and the CreateCustomFields2 method, as well as Project Web App, all allow you to create an enterprise project custom field of type Flag, and set the custom field to be workflow controlled. However, Project Server workflows cannot control Flag custom fields. You should not set project custom fields of type Flag for workflow control.

Project Server Permissions




Allows a user to modify the definitions of enterprise custom fields and lookup table values. Global permission.

If the user did not check out the custom fields, also requires administrative permissions to force check in.