The Grid component supports data paging. You can specify the page size and switch pages programmatically or via the Paging Panel’s UI controls. The paging state management, Paging Panel rendering, and built-in paging logic are implemented in the corresponding plugins. You can also configure the Grid to use server-side paging if your data service supports it.
The following plugins implement filtering features:
Note that the plugin order is important.
DxPagingPanel plugins to set up a Grid with paging.
Specify the active page index in the
currentPage property and subscribe to the
update:currentPage event. Use the
.sync modifier for two-way binding.
In the following example, the page size is specified using the
pageSize property. However, the
update:pageSize event handler is not specified because the page size is not supposed to be changed internally as the Page Size Selector is not available.
Assign an array of available page sizes to the
pageSizes property to enable page size selection via the UI. The Page Size Selector displays the ‘All’ item if the specified array contains an item whose value is 0. You can specify custom text for this Page Size Selector item using the
Specify the page size in the
pageSize property and subscribe to the
update:pageSize event. Use the
.sync modifier two-way binding.
You can handle the Grid’s paging state changes to request page data from the server according to the current page index and the page size if your data service supports paging.
Paging options are updated once an end-user interacts with Paging Panel controls. Handle paging option changes using the
update:pageSize events, and request data from the server using the applied paging options. Once the page data is received from the server, pass it to the
For remote paging, use the
DxCustomPaging plugin instead of the
When you use paging features with sorting, grouping, or filtering, take note of the order in which the plugins appear in the Grid’s container. You need to choose whether to paginate filtered rows or filter the current page. In the former case, put the
DxIntegratedFiltering plugin before the
DxIntegratedPaging one. Otherwise, inverse the plugins’ order.