FAQs about grid layouts based on templates

You might be using an old (legacy) grid design or a non-templated harness. Also, you might have placed the grid outside of the templated layout section.

Complete the following checks in sequence:

In run time, verify the grid layout table markup as the new design. See How can I tell whether a grid layout table is based on the old design or the new design?
If the markup indicates that the grid is the old design, then check to see if the harness is templated.
Next, check to see if the table is included inside any layout that does not use a template.
Make sure that the templated grid is placed inside of a templated layout.

What features of templated grids are supported in offline mode?

Grid sorting and pagination are supported in offline mode.

How do features behave if they are not supported in offline mode?

The following grid layout features are not supported in offline mode:

Filter
Group By
Column Toggle
Row Height
Refresh List

When clicked, the following UI controls display a pop-up window with the message, This action is not supported in offline.

Add
Edit
Delete

Why does a grid sourced from a parameterized data page not display in offline mode?

Specify the Custom populator to ensure that the parameterized grid is loaded in offline mode.

Why does a grid sourced from Property (PageList) display the Sort arrow but does not sort the table data?

If the Page List property is sourced from a Data Page, then correct the option to Copy from Data Page.

If the option Refer to Data Page is selected, sorting does not work.

Is Add from Outside supported in a grid sourced from Property (PageList)?

No. Add from Outside is not supported for grids sourced from Property (PageList). Optimized tables are predominantly for read-only page lists.

Edit is not supported in run time for grids sourced from Property (PageList). Although, you can specify this option in design time. However, the Edit modal dialog that displays in design time is confusing. Edit usually means that you can perform add, change, or delete actions. In this context, the Edit modal dialog allows you to perform a change action only; add and delete actions are not allowed.

Using the template pzGridModalTemplate, I have designed a grid with buttons to Open Local Action or Launch Local Action. Why does OnSubmit of the modal dialog box not work?

Any modal dialog box embedded inside a templated grid must refer to pyNexGenGridModalTemplate for the custom template.

Why? Because pzGridModalTemplate uses active grid.ctx, which is not supported for templated grids.

With row visibility set for client-side validation, why do I see the No Data error message on some pages but not on other pages?

Row visibility on the client is expected to behave the same for all pages because all the rows exist in the DOM. Client-side validation displays None based on client-side expression evaluation. All pages will be displayed.

For server-side row visibility, the pagination gadget is not displayed if the number of records satisfying the condition is smaller than the page size.

Can I filter by format in a templated grid?

No: Filter by format is not supported in templated grids.

An application section contains multiple read-only templated grids sourced from the same data page. When I apply a filter on one grid, why are all the other grids filtered?

This is a known limitation introduced in Pega Platform version 8.3.

Do not place more than one read-only templated grid in the same section.

An application section contains multiple read-only grids sourced from the same data page but with different Layout groups. Why do all the grids have the same Layout group as the first grid?

This is a known limitation introduced in Pega Platform version 8.3.

Do not place more than one read-only templated grid in the same section.

An application requires a grid embedded in a grid (a nested grid). Can I use all the features of a templated grid for a grid within a grid (nested grid) or a grid within a repeating dynamic layout (RDL)?

During design time, there is no restriction on using templated grids for grids within a repeating dynamic layout (RDL). However, using templated grids for nested grids (grids in grids) is not recommended. See Troubleshooting nested grid issues.

Is there a way to customize the display of the pagination gadget in a templated grid? Sometimes the pagination gadget displays at the top and bottom of the pages; sometimes it displays at the bottom only.

During design time, there is no way to customize the display of the pagination gadget. The pagination gadget is displayed at the top and bottom of pages for a templated grid if the toolbar options are not selected.

If any one of the toolbar options is selected at design time, then in run time the pagination gadget does not display at the top and bottom of pages.

With row visibility specified for a templated table layout, does Group By Count include the invisible rows?

The option Group By is not supported for templated grids with row visibility or cell visibility specified.

How does a templated grid with Group By This Column specified for all columns during design time appear in run time when the application section is loaded on the page?

The grid is grouped according to the order of the table columns in design time.

How does the Layout grouping of a templated grid appear on page load if the columns of the table layout are designed with a mix of properties and UI controls?

Example

Column 1 has a property.
Column 2 has a button.
Column 3 has a Section Include.
Column 4 has a property.
Column 5 has a property.

The table layout will be grouped in order of the columns with properties: Column 1, Column 4, and Column 5.

Limitations of grids based on templates

When designing applications with grids based on design templates, understand the following limitations:

The table grouping feature is not supported for mobile devices.
The actions Add, Edit, or Delete for a templated grid are from Property.
Actions with When conditions are not supported.
Actions with property values as arguments are not supported through Pega Platform version 8.3. This issue was resolved in Pega Platform version 8.4.
Keyboard navigation for actions is not supported.
Non-template controls in a templated grid are not supported.
Template grids require the use of the sortable API for drag and drop between columns. Within the same section, if an overlay is designed and opened and a column is dropped, the overlay is not dismissed because the event is not propagated. The expectation that the overlay is dismissed after the column drop is not met. The application user has to click explicitly somewhere outside for the overlay to be dismissed. This issue is not specific to template grid drag-and-drop. Even with a repeating dynamic layout (RDL), where the sortable API is used for row reorder, this issue is reproducible because the sortable API issue persists: The overlay is not dismissed on column drop.
Work processing is not supported.
When a check box is added to a column header, clicking this check box does not select all rows of the templated table grid as expected.

Support Doc