Skip to main content
BuyLog In
ASP.NET MVC Extensions
Search in…
Docs > Components > Grid View > Focus and Navigation > Paging and Scrolling > Endless Paging
All docs
V24.1
ASP.NET MVC Extensions
Prerequisites
Supported Browsers
What's Installed
Get Started
Upgrade to a New Version
Common Concepts
Components
Card View
Charting
Data and Image Navigation
Data Editors
Diagram
Docking and Popups
File Management
Gantt
Grid View
Bind to Data
Data Representation Basics
Filtering
Focus and Navigation
Focused Row
Selection
Paging and Scrolling
Data Paging
SEO Paging
Endless Paging
Vertical Scrolling
Virtual Scrolling
Horizontal Scrolling
GridView Fixed Table Layout Specifics (Scrolling and Column Resizing)
Keyboard Navigation
Data Editing and Validation
Export
Visual Elements
Examples
HTML Editor
Multi-Use Site Extensions
Pivot Grid
Reporting
Rich Text Editor
Scheduler
Site Navigation and Layout
Spell Checker
Spreadsheet
Tree List
Vertical Grid
Query Builder
Security Considerations
Redistribution and Deployment
Troubleshooting
Get More Help
.NET Framework API Reference
Client API Reference
Download CHM

Endless Paging

  • 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

    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.

  • SEO Paging

    In Endless Paging mode the grid does not support SEO Paging.