A stylized purple-and-blue dashboard displays a filterable data table with navigation icons and cloud database imagery.
Power Apps makers working with big lists have a new option coming in the modern Data Grid for canvas apps. They can have the grid load more records as users scroll, or show numbered pages with a set page size. Microsoft's roadmap item 580454 lists the feature as "In development." It shows general availability planned for December 2026, for Web, in the Worldwide (Standard Multi-Tenant) cloud. Microsoft says roadmap dates and descriptions can change, so treat December as a target.

Microsoft's Learn documentation for the Data Grid is already published and was last updated on 4 November 2026. It describes the properties in detail, so you can plan for the feature now.

A stylized purple-and-blue dashboard displays a filterable data table with navigation icons and cloud database imagery. What is changing​

Until now, the Data Grid has made a single fetch and shown what came back. Microsoft's October/November 2026 Power Platform feature update describes two new ways to browse incrementally. The Pagination property chooses how the grid loads and displays records, and PageSize sets the number of records per fetch or numbered page. The goal is to avoid loading the whole result set up front.

Existing apps keep their behavior unless a maker turns paging on. The default mode is Pagination.None.

The three Pagination modes​

Pagination accepts Pagination.None, Pagination.Auto, or Pagination.Number.

ModeWhat it does
Pagination.None (default)Makes one nonpageable fetch, subject to the app's data row limit. PageSize doesn't enable paging in this mode.
Pagination.AutoLoads more records from a pageable source as users scroll. For an in-memory table or collection, it shows the records already available and doesn't simulate server loading.
Pagination.NumberShows one page of records with first-page, previous-page, and next-page actions. It fetches more pages from a pageable source as needed.

PageSize takes a positive whole number. A blank, zero, negative, or invalid value falls back to 100, and a fractional value is rounded down. To turn paging off, set Pagination to None. Don't blank out PageSize.

Microsoft separates paging from virtualization. Pagination governs data loading and page boundaries. Virtualization governs how many rows the grid renders at once. Virtualization turns on automatically for large datasets. Enabling text wrapping on a column disables it, so keep wrapping off on big grids.

How to set it up​

Automatic loading

  1. Bind Items directly to a supported pageable data source. Set Pagination to Pagination.Auto and PageSize to a suitable value such as 100.
  2. An inline table shows the layout but doesn't demonstrate remote fetching.

Numbered pages

  1. Set Pagination to Pagination.Number.
  2. Set PageSize. Microsoft's self-contained sample uses five inline records with PageSize of 2, which gives three pages. That sample demonstrates the pager and page boundaries, not server retrieval.
  3. In the sample, searching returns the user to the first page of matching records.

Community write-ups describe these modes against SharePoint lists with more than 10,000 rows. They say the Number mode can let users change page size from a dropdown. Treat those as third-party demonstrations, not Microsoft guarantees.

Search and sorting: where delegation matters​

Search is the area most likely to trip people up.

  • Default search. DelegateSearch is false, so the grid searches only the records it has loaded. If the source has more records, the grid offers a load-more action during a search. A search with no matches among loaded records doesn't prove the remote table has none.
  • Source-wide search. Set Searchable and DelegateSearch to true. Then use the grid's SearchText output in an Items filter your connector can delegate. Microsoft's example for a Products table with a Name column and a grid called PagedDataGrid is Filter(Products, StartsWith(Name, PagedDataGrid.SearchText)).
  • Delegation is still your job. DelegateSearch doesn't make a formula delegable. It hands filtering responsibility to your formula. Check your connector's delegation support before using it on a large table. Microsoft also warns that a delegation warning might not appear for search.
  • Sorting. For sources that support server-side sorting, sorting a supported column re-queries the source in the new order. Neither search nor sort can reach records excluded by an upstream nondelegable formula.

Behavior to expect after changes​

  • Changing Pagination or PageSize returns the grid to page one. It also clears the search text and the active sort. Users, or your app logic, must reapply them.
  • Changing the Items formula rebuilds the paging source, so the grid uses the new results. Don't rely on a page number staying the same after changing Items, Pagination, or PageSize.

Output properties to interpret carefully​

  • CurrentPage is 1-based. In numbered mode it follows the pager. In automatic mode it follows the visible row range.
  • ItemsCount is the number of records loaded so far. It isn't the server total, and it isn't the number of rows on the visible page.
  • AllItemsLoaded means everything available through the current paging source has loaded. With Pagination.None, it becomes true when the single fetch finishes, even if the data row limit truncated the results. Don't use it as proof that a remote table is fully represented.
  • These are outputs. Don't assign formulas to them to build custom paging.

Practical takeaways​

  • This changes browsing, not retrieval limits. Pagination controls data loading and page boundaries. It doesn't bypass delegation limits in Items, connector limits, or the scope of a collection that is already populated.
  • Test search against a large source. Confirm the results are what you expect, particularly with the default DelegateSearch of false.
  • Don't show ItemsCount as a total. It would mislead users on partly loaded sources.
  • Plan around the date. The roadmap says December 2026. Microsoft hasn't called it released, and the schedule may move.

My read: this is a sensible fix for a familiar canvas-app problem, loading everything or hitting row limits. It still depends on a source and formulas that can page. For collections and inline tables, the new modes mostly change presentation. That is general analysis from the documentation, not a tested result.

 

References

  1. Power Apps: Browse data with automatic loading and numbered pages in Data Grid Microsoft 365 Roadmap 2026-11-17T19:05:12.369378Z
  2. Data Grid modern control in canvas apps - Power Apps learn.microsoft.com
  3. Microsoft Copilot Roadmap | Microsoft 365 microsoft.com