Troubleshooting grid issues in Power Apps

This guide helps you resolve the following grid issues that occur in a Power Apps model-driven app.

• Can't use sorting or sorting doesn't work correctly.
• Can't use column filters on a grid or subgrid or filtering doesn't work correctly.
• Can't edit data in the grid after enabling editing mode.
• Grid or subgrid displays incorrect content.
• Grid or subgrid doesn't display all the records.
• Grid filter for a lookup column doesn't show any suggestions.
• Modern Advanced Find doesn't work correctly.
• Nested grid doesn't display data.
• Quick Find doesn't return correct results.
• Some columns don't contain data.
• The overall record count doesn't match the displayed content.

Terms

1. Grid control - a control that's displayed on an entity page.
2. Subgrid control - a control that's displayed in a form or inside a reference panel.
3. View selector - a drop-down control that allows selecting the current view.
4. Ribbon command bar - the content-dependent button bar at the top of a page or form.
5. Subgrid menu - a content-dependent menu.
6. Quick Find - a search control that allows filtering the current view by typing a search string.
7. Column Editor - a tool that allows adding, removing, or reordering columns in the current view.
8. Modern Advanced Find - a tool that allows applying complex filters to the current view.
9. Column filters - a tool that allows applying simple filters to the grid.
10. Column sorting - a tool that allows sorting the grid content by one or more columns.
11. Status column - a grid column that allows selecting rows. It's also used for displaying row related messages.
12. Nested grid - a child grid that renders inside a grid or subgrid control.
13. Column header - the header at the top of the grid or subgrid control.
14. Jump bar - the alpha-numeric bar at the bottom of the grid.

Here are the screenshots of the terms:

Useful tools

• Power Apps Monitor tool
• Web Developer tool

Steps to perform before starting troubleshooting

1. Remove or disable custom scripts. One of the first steps is to ensure that custom scripts don't interfere with product functionality. It's highly recommended to perform this step even when custom scripts are used to work in one of the previous versions.

   • If all custom scripts are attached via form events, follow the steps in Troubleshoot form issues in model-driven apps to disable them.
   • Other custom scripts are added directly via web resources, custom solutions, or plugins.
   • If the issue can't be reproduced after removing custom scripts, investigate all the customizations to find the problem.
   • If custom scripts are correctly using publicly documented APIs and the product doesn't behave as expected, try to simplify the custom script to localize the problem. In most of the cases, 10-30 lines of script code are enough to reproduce an issue.

2. If the problem involves custom entities, custom relationships, custom views, custom configurations, or other custom resources, try to reproduce the issue with out-of-the-box (OOB) standard resources and avoid any custom resources. This method helps localize the problem.

3. Disable all the applicable business rules to see if the issue is caused by a business rule.

4. If reproducing the issue involves the use of third-party tools, try to reproduce the issue with standard OOB tools.