Easily Create a Read-Only Power Apps Subgrid Using Modern Controls

Learn how to replace deprecated legacy controls and easily create a read-only Power Apps subgrid by disabling inline editing in the modern grid control.

Keeping your model-driven app data secure from accidental changes is critical, and dealing with deprecated features can temporarily disrupt your workflow. Fortunately, transitioning to modern controls to lock down your subgrids is a straightforward process.

Problem Description: Deprecated Legacy Grid Control

In Microsoft Power Apps, the legacy read-only grid control has been deprecated, leaving many developers unsure how to properly lock down subgrids in their model-driven apps. When forms load with default modern controls, users may unexpectedly see the "New" button or have the ability to perform inline edits on records that are meant strictly for viewing.

Quick Answer for Locking Model-Driven App Records

To restrict edits, open your form in the Maker Portal, select the subgrid, navigate to the Controls tab, apply the Power Apps grid control, and toggle the inline editing feature to the disabled position. Once saved and published, the "New" button and inline edit capabilities will be hidden.

Likely Causes Behind Unwanted Inline Editing

• Feature Deprecation: Microsoft is phasing out legacy web client controls, forcing a migration to the modern Power Apps grid control which has different default behaviors.
• Default Grid Configurations: The modern grid control defaults to allowing inline editing if the underlying table permissions allow it.
• Missing Control Attributes: The subgrid was added to the form without explicitly customizing its control properties in the classic or modern form designer.

Recommended Solution: Configure the Modern Power Apps Grid

1. Log into the Power Apps Maker Portal and select the appropriate environment in the top right corner.
2. Navigate to Tables, select the table containing your form, and open the desired form in the form designer.
3. Click on the subgrid you want to make read-only to highlight it.
4. In the properties pane on the right side, locate and open the Components (or Controls) tab.
5. Click + Add Component and select the Power Apps grid control. Assign it to Web, Phone, and Tablet as needed.
6. Look for the property labeled Enable inline editing (or similar editing configuration) and set its value to No or disable it.
7. Verify your table and subgrid views are correctly linked.
8. Click Save and then Publish to push the changes live. The subgrid will now render without inline editing fields or the "New" record button.

Alternative Solutions for Restricting Record Modifications

1. Dataverse Security Roles: If users should never be able to edit these records anywhere in the system (not just on this specific form), modify their Security Role. Remove the "Write" and "Create" privileges for that specific Dataverse table.
2. Business Rules: Create a Business Rule that locks specific columns on the grid or form conditionally, though this is better suited for column-level restrictions rather than whole-grid locking.
3. JavaScript Form OnLoad: Use client-side API scripting to dynamically disable subgrid controls, though no-code methods (like the primary solution) are heavily preferred for long-term maintenance.

Working with WPS Office: Managing Exported Grid Data

Because Power Apps is a proprietary Microsoft cloud environment, WPS Office cannot directly alter model-driven app form controls. However, once you have your read-only Power Apps grids set up, users will frequently export that view data to Excel or CSV. WPS Office serves as an excellent, lightweight, and highly compatible alternative for opening, formatting, and analyzing these exported Microsoft Dataverse datasets locally. With WPS Spreadsheet, you can filter, chart, and present your exported Power Apps data entirely for free without requiring a separate premium office license.

Prevention Tips for Future Feature Deprecations

• Review the Microsoft Power Platform Release Wave documentation bi-annually to catch deprecated controls before they break your forms.
• Use the modern Form Designer by default rather than switching to the classic designer, ensuring you are applying the most current UI components.
• Standardize your organization's subgrid configurations by creating a template or documenting the exact toggle settings required for read-only deployments.

FAQs About Power Platform Data Grids

Why did Microsoft deprecate the legacy read-only grid?

Microsoft deprecated legacy controls to unify the user experience across the Power Platform and improve accessibility, performance, and responsive design on mobile devices. The modern Power Apps grid control replaces both the old editable and read-only grids.

Will users still see the "New" button if I only disable inline editing?

Disabling inline editing on the modern grid control typically suppresses the grid-level data entry options. However, if the "New" button still appears on the associated view's command bar, you may need to adjust the subgrid's command bar visibility using the Ribbon Workbench or modern command designer, or adjust the user's table creation permissions.