Defining tables to display data

 supports the following types of table fields:

• List view (see List-view-table-fields)
• Tree view (see Tree-view-table-fields)
• Cell-based (see Cell-based-table-fields)
• Alert list (see Alert-list-table-fields)
• Results list (see Results-list-table-fields)

These fields can be used by the client and the server. Depending on your needs, you might use the same table field in one context as a server-side table field and in another context as a client-side table field. The choice depends on whether you want to process the information about the client or on the server. 

When using table fields, remember this important distinction:

• Active links work on table fields on the client.
• Filters work on table fields on the server.

Client-side table fields enable users to view fields and requests from a form in tabular format. The set of requests displayed in a table is the result of a search of the table's source form. 

A server-side table field is any table field that appears in server-side workflow in filters or filter guides. You can use server-side table fields with filters to perform calculations on a set of records. For example, you can create filters to find a specific row in a table field (such as the last Entry ID) and then perform actions based on specific criteria. You can also use functions with server-side table fields. For example, you can compute how many records exist for a specified user or for all users.

Use filter guides to read the data in a server-side table. On a server-side table, executing a filter without a filter guide will not return any data.

Data in server-side table fields is read-only. 

The most important reason for using server-side table fields is network performance. When you perform actions on large amounts of data (for example, Push Fields actions), server-side tables improve performance because they do not use API calls from the client to the server. To lessen network traffic, use filters with server-side table fields instead of client-side table fields to communicate from a form in a browser through the  to the server and back through the  to the browser.

Display properties to support Progressive views

To Progressive views, the following Display properties are added for the Table fields:

• Toolbar Visibility—Specifies if the toolbar in a table field is visible (Values: True | False; Default value: True).
• Show Border—Specifies if the border in a table field is shown. (Values: True | False; Default value: True).
• Enable Row Reordering—Specifies if row reordering is enabled in a table (Values: True | False; Default value: False).
• Enable Nested Row Reordering—Specifies if nested row reordering is enabled in a table (Values: True | False; Default value: False).
• Order Column ID—Stores the order column ID. This is a text field.
• Active Link on Row Reordering—Stores the name of the active link for row reordering. This is a text field and is visible only when you select the True value for the Enable Row Reordering property.

• Active Link on Row Unselect—As a value for this property, you can specify the active link to be executed whenever you cancel the selection for a table row. Just click the ellipsis button in the Value column for this property, and then in the Active Link Selector dialog box, choose an active link.
  
  

  Important

  If you cancel the selection for one row, an active link gets fired. However, if you cancel the selection for all rows at once, the active link gets fired only once. At any time, if you refer to $ColumnID$ in the active link, you get the data of the primary selected row.

The following sections provide information about the types of tables and how to create and modify tables: