We have heard from our PowerApps makers that in creating apps, it is difficult to track down errors, and to figure out how to solve them.  We have also heard that it is hard to understand what needs to be done to create an accessible app. The App checker is now available to help provide a clear list of formula issues in your app, and to provide items to fix to make your app accessible. The App checker is an area that the PowerApps team will continue to invest in, and build on in order help to make debugging, performance and best practice decisions an easier and more guided experience.  

Formula error management

Using the App checker with formulas

There are two ways to launch the App checker for formulas. The first way is to select the App checker button in the upper right corner of the PowerApp studio.

This will launch the App checker where you can inspect Formula and Accessibility errors, warning, and tips.

Choose the Formulas chevron to drill into the list of all the errors and warnings for your app.

And, choose the chevron on the error to see additional details.

Note that this details pane doesn’t currently offer many additional details. We are currently working on adding more details for causes and “how to fix” suggestions for all errors and warning.

The second way is to double click on an error or warning indicator directly on the canvas. This short cut will take you directly to the error or warning in the App checker list. A single click on the error or warning indicator will still simply bring up the property in the formula bar.

Formula error indicator

A red dot will show on the App checker button if there are formula errors in your app.

The red dot does not appear for formula warnings, tips, or accessibility issues.

New badges for errors, warnings, and tips

Previously we showed errors with a yellow hazard triangle and suggestions as blue dots. We are moving to a more standard way of describing issues as shown in the chart below.

The big change is that delegation issues were previously classified simply as suggestions. They are now classified as warnings because of the potential for data loss. For example, if a Filter statement has a delegation warning it means that you may not get all your data, or even any of your data. And, if there is an assumption in your application that you have all the data from your data source, then your application could be wrong. Blue dots now represent Tips as is standard practice.

Accessibility Checker