Skip to main content
Version: 2023.1

Grid Pro - Introduction

Use cases

There are two main use cases for our Grid Pro component: simple data and connected data cases:

Simple data


A good scenario for this is when there's no need for streams or you're using a non-Genesis-based data source (e.g. a custom REST API).


This is also a scenario where our DataGrid could be used if the business requirements allow something more limited in features.

The simple data use case is when you have your own data model and flow (JSON, external/custom REST APIS, etc) but still want to use a rich data grid component with all its features (filtering, sorting, custom cell renderers, etc).

This use case requires the client app to handle all the data transformations/updates/deletes/cell renderers in the grid.

Connected data


This is the most common use case for Grid Pro component. When connecting to a Data Server or Request Server.


For this use case, a separate grid-pro-genesis-datasource component is required with a valid resourceName. More details here.

The connected data use case is when you have a Data Server or Request Server available/ready to use and don't want to worry about handling data transformations/updates/deletes/cell renderers in the grid (for cell renders it's flexible so you can use any component you want or the ones provided by default).


Attributes and props

  • autoCellRendererByType: boolean: Whether to automatically use a custom cell renderer for a given type. Defaults to false. When set to true will detect the metadata of the resource and use the appropriate cell renderer. We're currently supporting BOOLEAN, DATE and DATETIME types (with more to come soon).
    Defaults to 'false'.
    This will only work for Connected Data scenarios.

  • columnComponentName: string: EXPERIMENTAL | The name of the custom Column config component to be used for custom/extra column definitions. Defaults to 'grid-pro-column' but can be replaced with something else (keep in mind that we're expecting a definition prop, without it the slotted config won't work/tale place).

  • eventsAndCallbacks: any: The events and callbacks
    Default is empty, no overrides.

  • headerHeight: number: The height of the header in pixels.
    Defaults to '32' when using <zero-grid-pro>

  • onlyTemplateColDefs: boolean: Whether to use only the template column definitions (no extra column definitions).
    Defaults to 'false'.

  • rowHeight: number: The height of a row in pixels.
    Defaults to '32' when using <zero-grid-pro>

  • rowNodeId: string: The id to be used in each row.
    Defaults to 'ROW_REF' but can be set to any string (e.g. 'MY_UNIQUE_ID' from a Request Server query)
    This will only work for Connected Data scenarios.

  • theme: The theme to use for the grid.
    Defaults to 'ag-theme-rapid' when using <zero-grid-pro> and to 'ag-theme-alpine' when using <foundation-grid-pro>.

  • persist-column-state-key: Controls the persistence of the column's states (order, size, etc.) across sessions. Column state will not be persisted without this key. The persisted data is stored in the user's local storage in an object, keyed with this key if it is set, so each table must have a unique key in your application.
    Defaults to being unset which will mean the grid will not persist the column settings.

Default overrides

A given custom Design System may have its own Grid Pro variant, extending the base foundation-grid-pro and overriding the following by default:

  • theme attribute and its themeChanged event for custom style/theme related logic. See example below:
* Sets a CUSTOM default theme
* @override
theme = defaultRapidTheme;
themeChanged(oldValue: string, newValue: string) {
if (!oldValue && newValue !== defaultRapidTheme) return;
super.themeChanged(oldValue, newValue);
  • gridOptions setter for extending/adding extra GridOptions to the grid. See example below:
* Handles extra CUSTOM GridOptions configs
* @override
set gridOptions(options) {
options.components = {
[GridProRendererTypes.actionsMenu]: ActionsMenuRenderer,
[GridProRendererTypes.boolean]: BooleanRenderer,

const isDefaultRapidTheme = this.theme === defaultRapidTheme;
options.headerHeight = isDefaultRapidTheme ? defaultAgHeight : null;
options.rowHeight = isDefaultRapidTheme ? defaultAgHeight : null;

super.gridOptions = options;