[Expand]General Information
[Expand]WinForms Controls
[Collapse]ASP.NET Controls and MVC Extensions
 [Expand]What's Installed
 [Expand]Common Concepts
 [Expand]ASP.NET WebForms Controls
 [Collapse]ASP.NET MVC Extensions
  [Expand]Product Information
  [Expand]Getting Started
  [Expand]Common Concepts
  [Collapse]Grid View
    Overview - GridView
    Main Features - GridView
    [Expand]Binding to Data
    [Expand]Data Representation Basics
    [Expand]Data Shaping and Manipulation
    [Collapse]Focus and Navigation
      Focused Row
     [Collapse]Paging and Scrolling
       Data Paging
       SEO Paging
       Endless Paging
       Vertical Scrolling
       Virtual Scrolling
       Horizontal Scrolling
      Keyboard Navigation
    [Expand]Data Editing and Validation
   [Expand]Visual Elements
   [Expand]Member Tables
  [Expand]Tree List
  [Expand]Card View
  [Expand]Pivot Grid
  [Expand]Rich Text Editor
  [Expand]Site Navigation and Layout
  [Expand]HTML Editor
  [Expand]Vertical Grid
  [Expand]Data Editors Extensions
  [Expand]Docking and Popups
  [Expand]File Management
  [Expand]Data and Image Navigation
  [Expand]Multi-Use Site Extensions
  [Expand]Query Builder
 [Expand]Redistribution and Deployment
  Get More Help
 [Expand]API Reference
[Expand]ASP.NET Bootstrap Controls
[Expand]ASP.NET Core Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Office File API
[Expand]Report and Dashboard Server
[Expand]eXpressApp Framework
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation

Endless Paging

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.

Expanded 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 access 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 template technology, so it is not supported in Endless Paging mode either.

  • 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.

  • Binding to Custom Data

    The Grid does not support binding to custom data and Endless Paging mode at the same time.

  • Batch Edit Mode

    The batch editing it is not supported in Endless Paging mode.

Is this topic helpful?​​​​​​​