The Table Visualization allows you to select attributes from a tabular data set, and display them as a table. Table supports individual column renderers, which means the values for each attribute can have a customized presentation.
The example above has cell background color and text rules set up to show “heat” based on the number of visitors per month. See Rule Sets for more information.
Table configuration is broken out into the following steps:
A symbolic name used to represent this Visualization. This is the name that will show up in choosers when adding a Visualization to a Page.
Sets the default font size for the table.
Virtual Scrolling greatly improves performance of large datasets. It does this by displaying only a small amount of the available information at a time. This limits the DOM required, greatly speeding up the display. The downside is that in order for scrolling to work properly, virtual scrolling requires uniform row heights. To achieve this, the word wrap option within cell renderers will be disabled.
Disabling virtual scrolling means that ALL rows will be loaded. This option enables word wrap within cell renderers, allowing row height to grow and shrink based on the amount of text in a cell. This approach works fine for smaller data sets, but it can lead to performance issues if too many rows of data are returned.
Determines whether an end user can drag and drop columns to rearrange column order.
Determines whether an end user can hide/unhide columns at runtime.
An end user can show and hide table columns. The user’s visibility preferences will only persist for the current session. Once a user logs out, the column visibility will return to what was configured by the administrator.
The end user will be able to toggle column visibility using the icon, which will appear in the Visualization header.
Disables column hiding.
The icon will not be displayed in the Visualization header.
Determines whether the total row count is displayed in the table footer.
Determines how row background colors are applied.
This row shading option will remove the default alternating row colors, and allows an administrator to apply a static background color for all the rows.
This row shading option allows an attribute’s value to determine the background color of each row.
Background colors defined in column renderers will override the background color of a row.
This section groups together a set of properties that affect Column Headers in the table.
Determines a static color for all column headers.
Determines the font size for all column headers.
Determines the font style for all column headers.
This step determines which attributes in a dataset will appear as columns in the table.
Each Attribute Name in this list represents a column in the table. The columns will appear in the order displayed here.
This is used to override the raw attribute names in the data set with something better suited for display as a column header. This property defaults to the Attribute Name.
This specifies a width for each column. Width can be defined two ways:
This property only affects the column header. It allows you to set the data type of that column and position headers.
This property affects the default visibility of a column. When “Allow Column Hiding” has been set to Yes, columns that are hidden by default can be enabled at runtime using the icon.
This is a read only version of the column name from the previous step. It shows the display name, not the raw attribute name.
Cell Renderers combine multiple concepts together.
Editing a cell renderer  brings up a single dialog with all the options for the selected renderer type.
Table Renderers include:
See the Renderers section for more details.
This step allows an administrator to set a default sort for the table.
Shows a preview of what the Table Visualization will look like.
In edgeSuite v3.2 and higher, there is no longer a “Table selection mode”. The table’s selection behavior is determined through actions, and is achieved by using a condition on those actions. The example below shows how to make click actions behave differently based on a specific attribute within the record. The example shows a Set Page Variable action, but the same approach applies to a Switch to Page action.