Move to the Power Apps grid control before the old grids go away

Model-driven apps are consolidating onto one grid. Effective March 2026, Microsoft deprecated the Editable Grid control and the Power Apps read-only grid; they keep working with critical security fixes only, and the Power Apps grid control is the designated replacement for every view and subgrid.

What's deprecated, and what replaces it

What the new control brings, per Microsoft: infinite scrolling with selection up to 1,000 rows, inline editing, nested grids, grouping (except on lookup columns, and not with paging enabled), per-column aggregation (sum, min, max, average), and current accessibility standards.

Find where the old grids still run

The old controls hide in two places, and both need checking per table:

1. Table level — a grid control configured on the table applies to all its views.
2. Form level — each subgrid on a form can carry its own control choice.

Work from your solution: open each table's Controls tab, and each main form's subgrids, and note where Editable Grid or the read-only grid is set. There's no single tenant-wide report, so an inventory pass per app is the honest route.

Switch a subgrid on a form

1. In Power Apps, open the solution, the table, then Forms, and open the main form.
2. Select the subgrid; in the right pane expand Components, select + Component, and pick Power Apps grid control (or find it under Components > Grid in the left pane).
3. Configure it — editability included — then Done, Save and Publish.

Switch a table's views

Table-level control configuration still lives in the classic designer:

1. From the solution's toolbar choose … > Switch to classic.
2. Open the table (listed under Entities), select the Controls tab, Add Control, choose Power Apps grid control, Add.
3. Set it as the default for the client types you need, Save, Publish.

Configure and verify

Verify like a user, not a maker: open each migrated view and subgrid, edit inline where editing is expected, expand a nested grid, group a column, and check any form scripting that hung off the old grid's client API events. Grids with JavaScript extensions deserve a test pass of their own before the form ships. Record who verified which app — a migration isn't done because the control was swapped.

Pause animation

1. 1Inventory tables and forms
2. 2Swap the control
3. 3Configure editability
4. 4A person verifies each view
5. 5Publish

Sources

• Important changes (deprecations) coming in Power Platform — Microsoft Learn
• The grid control reference — Microsoft Learn
• Understand model-driven app views — Microsoft Learn
• Make model-driven app views editable using the editable grid control — Microsoft Learn