Edit text mode in a grouping

textmode=true

textmode=true<br>group.0.linkedname=project<br>group.0.namekey=view.relatedcolumn<br><strong>group.0.valuefield=project:name</strong><br>group.0.namekeyargkey.0=project<br>group.0.namekeyargkey.1=name<br><strong>group.0.valueformat=string</strong><br>group.1.linkedname=assignedTo<br>group.1.namekey=view.relatedcolumn<br><strong>group.1.valuefield=assignedTo:name</strong><br>group.1.namekeyargkey.0=assignedTo<br>group.1.namekeyargkey.1=name<br><strong>group.1.valueformat=string</strong>

Each line of code is preceded by this text. The lines of code that refer to the same field selected in the grouping are numbered with the same number, as follows:

• The first grouping of the report has a group number of 0. All lines referring to the first grouping start with group.0.
• The second grouping of the report has a group number of 1. All lines referring to the second grouping start with group.1.
• The third grouping of the report has a group number of 2. All lines referring to the third grouping start with group.2.
• Only in text mode, you can add a group number of 3, for a fourth grouping. All lines referring to the fourth grouping start with group.3.

Note: 4 groupings are not supported in the builder. They are only supported when using text mode. Workfront does not support more than 4 levels of groupings.

This is the name of the object or of the field as it appears in the database. For more information about how objects and fields appear in the database, see API Explorer.

The following scenarios exist:

1. If the name of the field you display is a phrase instead of a single noun, you must use camel case syntax for the valuefield. For example, for the Planned Start Date of a task the code is:

   Example: group.0.valuefield=plannedStartDate

2. If you want to display a custom field, the valuefield value is the actual name of the field, as you see it in the interface. For example, for a custom field named "More information", the code is:

   Example: group.0.valuefield=More information

3. If you want to group by objects that are related to other objects using the valuefield line of code the object names and attributes are separated by colons.

   For example, a grouping by Portfolio Name for a task list has the following value for the valuefield line:

   Example: group.0.valuefield=project:portfolio:name

   This indicates that from the object of the report (task), you can access the next related object (project); from there, you can access the following related object from project (portfolio); then the portfolio name (name).

For information about how objects connect to one another, see the section Interdependency and hierarchy of objects in Understand objects in Adobe Workfront.

Note: If you choose a field in text mode that is not valid in the standard interface and you switch to the standard interface, the grouping is deleted.

This line represents the format used to display the valuefield. The valueformat identifies whether an object or field displays as text, number, percentage, or date.

We recommend using HTML for your valueformat, especially when using valueexpression, to ensure the most accurate display of your information.

For information about additional values for this line, see Use conditional formatting in Text Mode.

You can add this line to replace valuefield, if you want to group your list by a calculation between several fields.

You must enclose the valuefield of the objects in curly brackets every time you use it in a valueexpression.

The following scenarios exist:

1. If you want to display the name of a grouping in upper case, you would use:

   Example: group.0.valueexpression=UPPER({valuefield})

   The valuefield of the object is spelled as it appears in the API Explorer.

2. If you want to add multiple valuefields by stringing them together in a valueexpression line, you must separate them by a period.

   For example, if you want to display the name of the portfolio in upper case in a task list, you would use the following code in the valueexpression line:

   Example: group.0.valueexpression=UPPER({project}.{portfolio}.{name})

   If you want to use a custom field in a valueexpression line you must precede the name of the field by DE: to indicate that it is a custom field. The name of the field is spelled as it appears in the interface.

   Important: When you use a custom field that is placed in a custom form section that has restricted permissions for some users, the calculation of the valueexpression is blank when those users view this calculation in a report. For information about adjusting permissions on custom form sections, see Create a custom form.

   For example, if you have a custom field labeled "Developer Name" and you want to group by this field and display it in upper case, you can use the following valueexpression to indicate this:

   Example: group.0.valueexpression=UPPER({DE:Developer Name})

   When referencing a Typeahead type custom field, use the following expression to reference the name of the object selected in a field labeled "Developer Name":

   valueexpression=UPPER({DE:Developer Name:name})

This line defines the grouping label. In this case it is using the abbreviated value based on the key.

If you want to modify the grouping name you can change this value to the following:

Example: group.0.name=Your Value

Name allows you to enter any text for the grouping name, while namekey requires you enter a key that is used to translate the name of a grouping.

To change the grouping name you can also add the displayname line, if one is not present.

You can add the following line to change the name of a column, which overwrites the namekey/name value:

Example: group.0.displayname=Your Value

We recommend removing all the lines that contain name when you rename a grouping.

group.0.iscollapsed=true

group.0.iscollapsed=false

• When you manually adjust groupings when viewing a list, Workfront remembers your manual preference until you log out. When you log back in, the list displays according to this setting.
• The results of a grouping always display expanded after accessing them from a chart element.