- 2 min to read
The grid's Endless Paging mode can be enabled by setting the ASPxCardViewPagerSettings.Mode property 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 card keys. Thus, the ASPxGridBase.KeyFieldName property should be specified so that the grid works properly.
Since the grid only creates portions of its hierarchy on the server side, visible card indexes can differ from the indexes on the client side. Therefore, it is recommended that you use the ASPxGridBase.FindVisibleIndexByKeyValue method to get the visible index of the actual card before using it (e.g., in the ASPxClientCardView.GetCardValues method).
In Endless Paging mode, a grid can be updated in two ways.
- A partial update is performed when loading a page. In this case, cards that are loaded on the client side are maintained.
- A full update is performed when filtering and sorting. 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. In Endless Paging mode, only the currently required data is created on the server. Thus, when the grid contains a template with a control, it cannot accesses the template data if the hierarchy has not yet been created on the server side. Therefore, in this mode, grid templates should be used for appearance customization purposes only.
- Master-Detail Grid. The master-detail grid implementation is based on the template technology, and thus is not supported in Endless Paging mode.
- Edit Form Template. Edit form templates do not work properly in Endless Paging mode. To use them, collect and update grid data manually on the client side.
- The server-side MakeCardVisible method. In Endless Paging mode, the ASPxCardView.MakeCardVisible method is not in effect.