Grid Column

Function: a!gridColumn()

Displays a column of data as read-only text, links, images, rich text, buttons, tags, record actions, or progress bars within the Read-Only Grid Component.

When configuring the component, click Display Options after choosing a value.

Parameters

Name	Keyword	Types	Description
Label	label	Text	Text to display as the column header.
Sort Field	sortField	Any Type	The name of the field that the data should be sorted by when the user sorts by this column. When sorting record data, reference a record field using the recordType! domain. For example, recordType!Case.fields.caseName.
Help Tooltip	helpTooltip	Text	Displays a help icon in the column header with the specified text as a tooltip.
Display Value	value	Any Type	The value to display in each cell within the column. The value can be text, a!imageField(), a!linkField(), a!richTextDisplayField(), a!tagField(), a!buttonArrayLayout(), a!recordActionField(), or a!progressBarField(). It is evaluated once for each row. You can reference the fields from the data source using fv!row and the field name in dot notation (fv!row.fieldName). For example, if your source is a data store entity, you can reference the "status" field using fv!row.status. You can also reference the identifier of the row using fv!identifier.
Visibility	showWhen	Boolean	Determines whether the column is displayed in the grid. When set to false, the column is hidden and is not evaluated. Default: true.
Alignment	align	Text	Determines the alignment for the header label and all values within the column. Valid values: "START" (default), "CENTER", "END".
Width	width	Text	Determines the column width. Valid values: "AUTO", "ICON", "ICON_PLUS", "NARROW", "NARROW_PLUS", "MEDIUM", "MEDIUM_PLUS", "WIDE", "1X", "2X", "3X", "4X", "5X", "6X", "7X", "8X", "9X", and "10X".

General Notes

• If the value for a column is empty or null, the grid still renders the column with just the label.

Column Width Notes

• For columns using the "AUTO" width, the width is determined by the length of the longest value in that column.
• Avoid using "AUTO" and weighted column widths (such as "1X", "2X", "3X", etc) together.
• If you use a fixed width (such as "NARROW", "MEDIUM", etc) for a column that doesn't take up the width of the page, the width will auto distribute depending on the content inside the column.
• If you use "ICON" & "AUTO" widths together, the column using "ICON" will always be the same width and the column using "AUTO" will fill up the remaining space.

Old versions

There are older versions of this Interface Component. You can identify older versions by looking at the name to see if there is a version suffix. If you are using an old version, be sure to refer to the corresponding documentation from the list below.

Old Versions	Reason for Update
a!gridImageColumn	Now supports multiple interface components.
a!gridTextColumn	Now supports multiple interface components.

To learn more about how Appian handles this kind of versioning, see the Function and Component Versions page.

Related Patterns

The following patterns include usage of the Read-Only Grid Column Component.

• Aggregate Data from a Data Store Entity and Conditionally Display in a Chart or Grid (Reports, Charts, Query Data, Grids): Aggregate data from a data store entity, specifically the total number of employees in each department, to display in a pie chart.

• Aggregate Data from a Data Store Entity on a Date or Date and Time Field (Reports, Query Data, Grids): Aggregate data from a data store entity, specifically the total number of employees by datet.

• Conditionally Hide a Column in a Grid (Grids, Conditional Display): Conditionally hide a column in a read-only grid when all data for that column is a specific value.

• Configure a Chart Drilldown to a Grid (Charts, Grids, Query Data): Displays a column chart with aggregate data from a record type and conditionally shows a grid with filtered records when a user selects a column on the chart.

• Configure a Chart to Grid Toggle (Charts, Grids): Display a column chart with a toggle to display an alternate grid view of the data.

• Delete Rows in a Grid (Grids): Delete one or more rows of data in a read-only grid.

• Display Last Refresh Time (Auto-Refresh, Grids): Display the last time the interface was updated, either based on a user interaction or a timer.

• Display Processes by Process Model with Status Icons (Grids, Images, Reports): Use an interface to display information about instances of a specific process model.

• Display a User's Tasks in a Grid With Task Links (Grids, Reports, Looping): Display the tasks for a user in a Read-Only Grid and allow them to click on a task to navigate to the task itself.

• Drilldown Pattern (Grids): The drilldown pattern allows users to select an item from a grid to see more details in place of the grid.

• Drilldown Report Pattern (Grids, Charts, Reports): The drilldown report pattern consists of a bar chart and column chart, which each drill down into a grid.

• Filter the Data in a Grid (Grids, Filtering): Configure a user filter for your read-only grid that uses a record type as the data source. When the user selects a value to filter by, update the grid to show the result.

• Filter the Data in a Grid Using a Chart (Charts, Grids, Filtering): Display an interactive pie chart with selectable sections so that a user may filter the results in a grid.

• Grid With Detail Pattern (Grids): The grid with detail pattern allows users to select an item from a grid to see more details next to the grid.

• Grid with Selection Pattern (Grids): This pattern is an example of good UX design for a grid that allows users to select items and easily view their selections when there are multiple pages of data. It also provides information on a common save behavior.

• Limit Grid Selection to One Row (Validation, Grids): Limit the number of rows that can be selected to one.

• Limit the Number of Rows in a Grid That Can Be Selected (Validation, Grids): Limit the number of rows that can be selected to an arbitrary number.

• More-Less Link (Grids, Rich Text): Use this pattern to keep grids with rows containing varying text lengths looking clean and uniform. This design also improves readability and the user experience by limiting the amount of text in the interface.

• Refresh Data Using a Refresh Button (Auto-Refresh):

• Save a User's Report Filters to a Data Store Entity (Grids, Smart Services, Filtering, Reports): Allow a user to save their preferred filter on a report and automatically load it when they revisit the report later.

• Searching on Multiple Columns (Grids, Filtering, Reports): Display a grid populated based on search criteria specified by end users.

• Show Calculated Columns in a Grid (Formatting, Grids): Display calculated values in columns in a grid.

• Use Links in a Grid to Show More Details and Edit Data (Grids): Allow end users to click a link in a read-only grid to view the details for the row, and make changes to the data. The data available for editing may include more fields than are displayed in the grid.

• Use the Write to Data Store Entity Smart Service Function on an Interface (Smart Services, Grids, Looping): Allow the user to publish several rows of data to a table through the a!writeToDataStoreEntity() smart service function.