Endless Paging

• Aug 01, 2019
• 2 minutes to read

In the Grid View, Endless Paging mode allows grid rows to be loaded on-demand, based on user actions.

The grid’s Endless Paging mode can be enabled by setting the ASPxGridViewPagerSettings.Mode property (using the GridViewSettings.SettingsPager .Mode ) to EndlessPaging.

In Endless Paging mode, the grid hierarchy is created on the server side, and is sent to the client side on demand based on user actions. The hierarchy is created based on row keys. Thus, the GridSettingsBase.KeyFieldName property should be specified, so that the grid will work properly.

Since the grid only creates portions of its hierarchy, the visible indexes of the rows on the server side can differ from the ones on the client side. Therefore, it is recommended that you use the ASPxGridBase.FindVisibleIndexByKeyValue method (using the MVCxGridView .FindVisibleIndexByKeyValue ) to get the actual row’s visible index before using it (e.g., in the ASPxClientGridView.GetRowValues method).

In Endless Paging mode, a grid can be updated in two ways.

• A partial update is performed when loading a page, expanding/collapsing a group, or expanding/collapsing a detail row. In this case, rows that are loaded on the client side are maintained. The header, footer, etc., are not updated.
• A full update is performed when filtering, sorting, grouping, and dragging columns. As a result, the view on the client side is not synchronized with the data on the server side, so the data should be reloaded.

Endless Paging Mode Limitations

• Templates

• Master-Detail Grid

• Edit Form Template

• Binding to Custom Data

• Batch Edit Mode