Skip to main content
Planview Customer Success Center

Configuring Available Fields

The Available Fields screen provides a list of PPM Pro-supplied ("standard") fields for the selected entity. You can create fields to add to this list (referred to as user-defined fields, or "UDFs"), or hide fields that your organization doesn't need. Once you have your list of fields, you can modify their properties. For example, you can change a field title, determine whether to make the field available for use in reports or filters, and make the field required.

Note: All entity types have an Available Fields page. This topic uses screenshots from the task entity as an example.

Restricted and Unrestricted Fields

Standard out-of-the-box fields and UDFs are initially "unrestricted," which means that any user type or member of any team can view and edit the field. Most entity fields are unrestricted.

If you want to limit field access to a certain user type or team, you create a restriction. A restriction gives privileges to a user type/team, and as a result, everyone else (other user types or team members not included in the restriction) no longer has access to the field. The field is now referred to as a "restricted" field. See Creating Restrictions for more information. When you create a restricted field, additional properties become available - see Restricted Field Properties below. Note that field restrictions apply across categories.

If using the PMO team feature, see  Restricting Settings Fields to PMO Team Members and PMO_Field-level_Restrictions.

Hidden Fields

If there are standard fields that you know your organization does not need, you can hide them by selecting the field and clicking the Hidden radio button on the Properties panel. If you have created UDFs that you don't want, simply delete them by selecting the UDF and choosing Actions > Delete (provided they are not referenced elsewhere in the product). Note that if you hide a field, it will not be available for use in Reports or Filters.

Note you can create restrictions by "hiding" fields for certain users/groups by using the Able to View on Details = No property, while making the same field available for reports or filters; see Creating Restrictions.

Setting Field Properties

The screenshot below shows the Available Fields page.


To view/edit a field's properties, select the field from the Available Fields list; the Properties panel (right-hand side of the page) will display the properties.

  • Common properties - Properties whose values will be the same across categories and restrictions. (Note: Additional field properties are displayed when you create a restriction, and are noted in the table below.) Configure these properties regardless of whether you have or plan to have restrictions on the field, or whether you plan to create categories. If you do create restrictions or categories, these values will apply to the field if it's restricted or unrestricted, or whether it is used in one or multiple categories.

For example, if you create restrictions for members of two groups (Administrator group and Resource group), the field Title value will be the same for each group, as well as the ability to use or not use the field in Filters and Reports, and the labels for the Detail and Grid display names.

  • Variable properties - Properties whose values can be different across restrictions. If there are no restrictions, the values can vary across categories; changing these values in Available Fields will not change existing settings in Details. If you don't have any restrictions or categories other than the default, the Variable properties behave like Common properties because the field is unrestricted and used in only one category. If you have restrictions, you can set the variable properties to different values for each restriction. Note that if you do create a restriction, additional Variable properties called "Able to View on New Details" (not available for the task entity) and "Able to View on Details" appear in the Variable Properties list. You can configure this set of properties differently for each restriction. See the screenshot below.

For example, you can create restrictions for members of two teams (Administrator group and Division Group). You can make the field able to view on new and editable for members of the Administrator group, but not able to view on new and read-only for members of the Division Group by setting Able to View on Details = Yes - Editable and Able to View on New Details = Yes - Editable for Administrator, and setting Able to View on Details = Yes - View only and Able to View on New Details = No for the Division Group. When you place these fields on the Details panel, those properties will control the users' ability to view/edit. See Creating Restrictions for more information.

  • Note: Many standard field properties are read-only; these properties are provided to show how/where the field is being used. Appropriate properties are editable for UDFs.

Example: Restricted Field Properties - Administrator Group


Example: Restricted Field Properties - Division Group


If you are not creating categories or restrictions, all properties are the same to you.

Create a new field (UDF)

  1. From Admin/Setup/All Entities/Financial Entries/Available Fields, choose New > fieldType. (Note that fieldType represents the field type you pick from the menu.)

The New fieldType dialog appears. Note that when you create a UDF you will be presented with the many of the same properties that you saw for standard fields. You can accept the default values and tweak them later in the Properties panel. Refer to the table below for property definitions.


  1. Click Save.

Any values you chose or entered will be displayed in the properties panel on the right-hand side. You can edit the properties inline at any time. If you make any changes, don't forget to click Save.

Field Property Definitions

The following table contains a superset of all the properties you might see for a field.

Common Properties



The name of the field. This value will be used for the Detail Display name and the Grid Display Name, unless you override in each field, respectively. If you are editing a standard field, you can change the title.


Optional text describing the field. If you display the Description field in the Details pane or on the grid, the text you enter here will be displayed. Note that if you see a $token in this field it means that your organization has used the data dictionary to change the out-of-the-box name of this entity. The end user will see the result of the substitution.

This text appears as hover text when the user holds the cursor over the field label.

Field Type

A read-only field that displays the field type of either the UDF you are creating, or the field you are creating a restriction for. You selected the field type from the New menu.

Custom (UDF) string fields have a limit of 4000 bytes for English-language content. Double-byte languages will have a lower limit, possibly as low as 1,000 bytes (for 4-byte languages, for example).

Custom (UDF) text box fields have a limit of 10,000 bytes.

List to Use

(List fields only) Contains all the existing lists you can associate with the list field. Before you create a list field, you need to make sure you have created an appropriate lookup/status list. See Creating a Lookup List. For Standard list fields, "Field Sub Type" is used instead of "List to Use," and is read-only.


(List fields only) For any list based on a filterable entity, this field displays any existing filters based on the entity. Does not apply to status, lookup, or custom lists.

Display Option

(Boolean, Number, String fields) Settings that control the display of the data in the field.

Boolean: Checkbox, Yes/No, True/False

Number: Integer, Money, Percent, Native Percent, Float, Non-Negative Float

String: Telephone, Email Address,  HTML Display, String (Note: Group Header is presented as a Display Option - do not use it, it will be removed as an option in an upcoming release.)

Field Length

(String fields only) Determines the default width of the field.

Show on Reports

Controls whether the field is available for use in reports.

  • All - the field appears in the All folder

  • All & Common - the field appears in both the Common and All folders.

  • None - the file is not available for use in reports.

Show in Filters

Yes - The field is available for use in filters

No - The field is not available for use in filters

Detail Display Name

By default, the Title of the field is used as the field label in the Details panel. If you want the field name in the Details panel to be different than the Title value, enter it here.

Grid Display Name

By default, the Title of the field is used as the column title in the Grid. If you want the column title to be different than the Title value, enter it here.

Calculation Class

Note: For numeric fields, you must specify a calculation class in order for the field to be available as a data series field in reports. Please note the following recommendations:

  • Integer/Money fields - use Min-Max-Avg-Sum

  • % fields - use Min-Max-Avg

  • Date fields - use Min-Max

Variable Properties


Field is Required

Enable this property if you want the field to be required when creating the entity.

If PPM Pro has marked a standard field Required at Available Fields, you cannot override it on Details. Other standard fields (that are not marked Required), can be marked Required only at the Details level.

Note: System-maintained fields and read-only fields such as Customer, Department, Source Request and Last Modified Date cannot be marked required or have default values. Boolean fields cannot be required.

Default Value

The Default Value only applies when creating new entities; it does not apply to existing entities.

You can specify a default value on the Available Fields page and/or on the Details page. The value of the Default Value field in the Available Fields page is used when you add the field to the Details page for an entity Category. You can then override the default value (perhaps you want a specific value for a specific category) or use the value from the Available Fields page. Note that changing the Default Value for a UDF in the Available Fields will not change the Default Value on the Details page for the same field.

The Default Value on the Details page is used as the actual default value for the required field in the current category. You can specify a different default value for the field when it is used in another category.

If there is a default value specified at Available Fields and you delete the value in the Details, the field will use the value from Available Fields (the Default Value field will be empty at the Details level).

Date fields cannot have default values; the Category field cannot have a default value (the default category is configured on the Categories page for entities that allow a default).

Show on Grid

(Appears for restrictions only) Check this property if you want if you want the restricted users/teams to be able to see the field IF it is placed on the Grid; other users that do not meet the restriction will not see the field in the grid even if it is placed on it.

An unrestricted field is, by default, available to use as a grid column (but you won't see the Able to View on Grid property).

Show on New

(Restrictions only) (not applicable to tasks) Yes - Editable, Yes - View Only, No. Determines whether the field can potentially be viewed/edited in the New Entity window when creating an entity. If you have multiple restrictions, you can set this property to a different value for each restriction.

The setting here serves as the default to the Show on New Details property on the Details page.

Show on Details

(Restrictions only) Yes -  Editable, Yes - View Only, No, Yes - Editable (PMO only). Determines whether the field can potentially be viewed/edited when editing an entity.  If you have multiple restrictions, you can set this property to a different value for each restriction.

The setting here serves as the default to the Show on Edit Details property on the Details page. See About_PMO_Locking for information about the Yes - Editable (PMO only) option.

Note that there are two additional properties on the properties pane that are not shown in the New Field dialog: Method ID and Field Origin. Method ID is a unique identifier that is used by the API to differentiate multiple fields with the same name but different display types. Field origin displays either Standard (PPM Pro-supplied field) or User Defined (a user-created field).

View Field References

A field reference is the presence of a field in filters, reports, calculated fields, entity details, or as a grid column. Mouse-over the references_icon.png icon to see the number of references. Click references_icon.png to display a window that lists where the field is in use. Note that if a field is used multiple times in one filter or report, for example, that filter will appear multiple times in this list. (You can also select the field and choose Actions > View References.) For example, in the example below, the "Status" field is referenced in reports and filters, but is not used in calculated fields. Each tab displays the actual references:

          references_reports.png .  references_filters.png .  references_calc_fields.png

If there is no references_icon.png icon, then the field is not used anywhere. This is useful information to determine the impact of removing/deleting a field.

Deleting UDFs that have References

You cannot delete a UDF if it has one or more associations (the Delete menu option will be disabled in such cases). To delete a UDF with one or more references, you will first need to go remove the UDF from those references.