Editable Grid and Read-Only Grid Now Get Security Updates Only

Since March 2026, the controls "Editable Grid" and "Power Apps Read-Only Grid" are deprecated in model-driven apps. They only receive critical security fixes and no new features. Both keep working for now. After that, according to Microsoft, support ends. Microsoft has not named a date yet.

This is not an acute shutdown. But the successor is settled, and anyone who starts now can plan the switch calmly.

What is affected

Both controls show records in views and subgrids. The Editable Grid also allows direct editing. It is a popular tool when users need to maintain many rows quickly, such as the line items of a quote or time entries. According to Microsoft, the Read-Only Grid was a transitional solution and is no longer needed.

The successor for both is the "Power Apps Grid Control". It can read and edit in one control. Among other things, it brings grouping, totals and nested grids. Microsoft also justifies the change with accessibility: the Editable Grid no longer meets current standards.

Why switching now pays off

If you switch today, you do it calmly and not under time pressure when a future platform version actually turns off the old control. A form that is being touched anyway is the cheapest moment for the change. The second adjustment on the same form costs almost nothing extra, because testing and acceptance are due anyway.

Plan for one point here. Customizations on the old Editable Grid cannot always be carried over one to one. JavaScript that hooks into grid events (for example when a cell changes) belongs on the checklist, as do configurations of individual columns. The Power Apps Grid Control has its own options for this, but the transfer is manual work.

How to find the controls

In the solution export, both controls appear by name in plain text. You find them in the element "customControl" in "customizations.xml". The Editable Grid is called "MscrmControls.Grid.GridControl" there, the Read-Only Grid "MscrmControls.Grid.ReadOnlyGrid". A simple text search for these two names finds every place in the export. Do not confuse them with "MscrmControls.Grid.PCFGridControl". That is already the successor, so there is nothing to do.

Most hits are in forms, usually on a subgrid. A table can also have such a grid as its default control. It is then not in the form but in the table's block under "CustomControlDefaultConfigs". Anyone who only reviews the forms easily misses this case.

For context, since I built an audit tool with D365 Audit myself: it searches for exactly these two names. It reports every affected form with the number of affected controls, plus tables with such a grid as default. A subgrid counts once, even if the export lists it separately for each device type. A plain text search often finds it in far more places than are actually relevant. In the example exports against which I tested the rule, this affects a small share of the forms (in one of them 9 of 62) and is not the normal case. What is not in the export, the check naturally does not see, for example settings made only in the target environment.

What I would do now

Create a list of the affected forms and switch each one during the next functional rework. Forms that nobody will touch in the foreseeable future go on resubmission, at the latest when Microsoft names a date for the end of support.

Source: Microsoft Learn, "Important changes (deprecations) coming in Power Platform".