Skip to main content
Planview Customer Success Center

Supported data and display types

A calculated field in PPM Pro can output one of several data types, such as Integer, Float, or String. Within each of those data types, you select a single display type.

The String data type supports String, Textbox, and HTML display types. Note that calculated fields expecting to output HTML must declare themselves as HTML display type. If a field has an incorrect Display Type, its value may show up with markup on the page or report - for example: “<span style="color:red>High</span>" will show in the cell rather than: "High".

Correcting any problem that arises from this is as simple as editing the calculated field and changing its Display Type to accurately reflect its output.

Note to existing users: Until the July 2017 release we treated String and HTML display types the same, allowing HTML markup in the output from calculated fields declared as String, rather than HTML. If you have not been declaring the HTML display type for these fields, you will need to update them. This change was in response to security requirements regarding the handling of HTML,

The following table shows supported calculated fields data types and their associated display types.

Data Type

Display Type

Boolean

Yes/No (default)

 

Checkbox

Local Date

Date (default)

Local Date Time

Date & Time

Float

Float (default)

 

Money

 

Percent (see note)

 

Native Percent

Note: Data entered in a Native Percent field is assumed a percent and stored and displayed as is, with report output adding a '%'. A Percent field expects a decimal and multiplies the displayed value by 100. For example, if you enter 25 in a Native Percent field, the UI displays 25, and report output displays 25%. If you enter .25 in a Percent field, the UI displays 25, and reports output displays 25%.

Instant

Date & Time with time zone (default)

 

Date only

Integer

Integer

Integer - No format

String

String (default)

 

Text box

 

HTML

PPM Pro strongly suggests not using calculated fields to inject HTML. This technique assumes a specific layout and structure of the project (user interface and reporting). The current project output is not a contract and will change in the future.

 

Column header