Calculated custom fields vs. calculated columns
To aggregate several fields in Adobe Workfront and display that aggregate value in a new field, you can create the following:
-
A calculated custom field in a custom form
For more information about adding a calculated custom field to a custom form, see the section Add a calculated field to a custom form in the article Add calculated data to a custom form. -
A calculated column in a view
For more information about using calculations in a view, see the section Use Text Mode in views in the article Overview of common uses for Text Mode.
Although you use text mode to build both calculated fields and calculated columns, the syntax for building them differs. Refer to the articles listed above to learn how to build calculated fields and calculated columns. For information about the different syntax used in calculated data expressions such as calculated custom fields and columns, see the section Syntax of calculated custom fields vs. calculated custom columns in this article.
You can use the same calculations in both calculated fields as well as a calculated column. However, depending on what your purpose is for these calculations, you might want to consider building one versus the other.
Syntax of calculated custom fields vs. calculated custom columns
Although the functions that you use are the same, the syntax for building an expression in a calculated custom field can be different than it is for building a calculated custom column.
For example:
-
In a custom field, on a custom form for tasks, you would use the following to generate the name of the parent project of the task where the custom form is attached:
{project}.{name} -
In a custom column in a report, you would use the following to add a Project Name custom column on a task report:
valuefield=project:nameOr
valueexpression={project}.{name}note tip TIP The same syntax applies to all text-mode reporting elements where calculated expressions are used: views, filters, groupings, and prompts.
The differences between the two syntaxes are:
For more information about the syntax you must use in a calculated custom column, see Text Mode overview.
When to use calculated custom fields
- When you want to group the aggregated results in a report or you want to show this information in a chart
- When you want to aggregate the data beyond the aggregation that is calculated in the field
- When you are not concerned about the timeliness of the data, as data is not updated and it might change over time
Actions that trigger the update of a calculated custom field
-
On an object’s main page, clicking the More icon
-
Bulk editing multiple objects when Recalculate Custom Expressions is enabled
-
Editing a custom form when Update previous calculations is enabled for the calculated custom field
When to use calculated columns in a view
-
When you want real-time data to be available on a report.
Calculated views are always fresh because the calculation is made when the report is run or the view is applied.
-
When you have no plans to group by aggregated results nor use this information in a chart.
-
When you do not plan to aggregate the data beyond the aggregation that is calculated in the column (data can be aggregated only once).
-
When you want the calculation to include a reference to the current date using the $$TODAY or $$NOW wildcards.
note tip TIP Do not use this reference in calculated custom fields because they only recalculate when the attached object is edited. These types of calculations become outdated.
Examples of calculated custom fields and columns
For examples of calculated custom fields, see Calculated custom data in reports.
For examples of calculated custom columns in views, see the following articles: