Leveraging the Power of Solution Checker from Power Apps

If you started your implementation with an older version of Dynamics CRM and had converted to the latest version or to using Unified Client Interface, and you want to ensure that your solutions are written based on best practices, Solution Checker will come in handy.

December 2018 when Microsoft started to feature it in public view. Based on the customers that used it, it helps them in resolving lots of issues and have seen 20% performance increases on their form loads.

How to get started? Go to the Power Apps portal and head on to Solutions. Select the solution you would like to check, and you will see the Solution Checker button.

For first time users, it will show you an option to install the solution. Installing it will direct you to the AppSource site. Click on Get it now, and it will redirect you to a page where you need to select the environment you would like to use it for. Click Agree and wait.

AppSource: PowerApps Checker
Note: Every new and existing CDS for Apps environment will now have the solution installed automatically

Before you are able to run it, make sure you have the proper Security Roles in your common data service environment. Two of the required permissions are Export Customizations and Solution Checker.

Required Security Roles to run Solution Checker

You know when it’s done when Power Apps sends you an email with the high level results.

What I really like about Solution Checker is the flexibility to review the results. You can easily view the results in multiple ways: online (make.powerapps.com), during export or in your local drive. Reviewing results online will give you the ability to filter results in different helpful ways.

Viewing Solution Checker results online

The cool thing about this checker is, it can detect missing functions that are set in your form properties’ onload, onsave and on change events. Example error: An event registration entry was detected on the form Contact for the entity Contact for the event onload where the function does not appear to exist in the referring web resource script, [name of the web resource file]. The function name defined is [name of function]. This will likely cause issues when trying to invoke the event.

Example of an actual medium severity result

I hope this helps you improve the quality of your solutions. Let me know in the comments below how this helps you or if you would like to share some tips for everyone to learn.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s