Solution checker enforcement public preview

[JesseParsons]

Please use this thread to discuss feedback/suggestions/concerns on solution checker enforcement.

See our documentation for more information.

[sperry1625]

The release notes are a little thin.

Some questions:

1. Which Solution Checker results does it look at?
2. Does this work with DevOps release pipelines?
3. If it does work with DevOps, how does the import know what solution results to use?

I have more, but they are based on the answers to the above.

[sidg]

Hi there,

Thanks for the questions. Here's my take - 

1. Solution checker enforcement looks at the outcome of the solution checker results (not the results itself) from the last solution checker run, irrespective of which environment in the tenant they're in. This will be valid as long as the contents of the solution don't change or for 90 days since the last solution checker run.
2. Yes, irrespective how a solution is imported, enforcement will try and verify the quality of the solution and depending on the setting will either warn or block the operation and notify the admins.
3. Answered as part of #1.

Looking forward to your follow-up questions.

-Sid

[sperry1625]

Scenario

Environment 1: [DEV] BizApps

Environment 2: [UAT] BizApps

Environment 3: BizApps

Application is built in Environment 1. Solution checker run in Environment 1.

Flow 1

Solution is exported then imported into environment 2, for the first time.

Questions

1. What check is performed?
2. How does the import process know where the results of the Solution Checker is in order to verify?

Flow 2

Update made to solution in Environment 1, Solution checker run again.

Solution exported and imported to environment 2.

Questions

1. What check is performed?
2. What solution checker results are verified?
3. How does it know where the results are?
4. Are results part of the export package?

Solution checker cannot be run on imported managed solutions, so the solution won't have results in its new environment.

Am I missing something? Not understanding a detail on how and what is actually included in an export and import?

Thank you.

[sidg]

Verification checks are performed centrally and are not bound to environments.

In both the scenarios you mentioned above -

Since solution checker is run/re-run in env 1, results are stored in env 1 and a basic summary of these results (count of failures & results location) along with a hash are stored centrally. During solution import, the hash is used to verify if the solution passed verification or not. Depending on the types of failures and the enforcement setting (warn/block) appropriate action is taken.

Hope this clarifies.

[TxH]

Is the new feature Rule exclusions mentioned in this blog post still being rolled out or should it already be working?

I'm having the issue that the Excluded Rules Dropdown-List cannot be opened in any of my environments (Developer, Sandbox, Production) in Europe and US.

[JesseParsons]

Thanks for reporting!  We have identified the issue and reproduced internally.  We may choose to hide this dropdown until the fix is fully released, but we should have a solution soon for the dropdown not opening.

[jjpreston291]

Hi,

Issues identified as Critical include minor Canvas App formula mistakes.

I agree these should be flagged but as Power Platform Admin, I'm concerned about 'block' solutions with critical issues for things like this.

Will the Exclusion list allow us to exclude this ? Plus there may be other things that I do not class as Critical. I read above , and can see in our CoE that there is a central storage of solution histories but there is no easy way to view all the critical issues for me to see whats' critical.

Thanks in advance

[JesseParsons]

Hello,

You can check out Use solution checker to validate your solutions - Power Apps | Microsoft Learn for a reference of rules by severity, including those marked as Critical.  Of these, app-formula-issues-high is likely the one you are referring to.  Are there particular formula issues you are looking at that you feel should be lowered in severity?  You can exclude this rule in the Managed Environment settings panel by checking the box next to "Fix high severity formula issues".  Please let us know if you have more questions!

[jjpreston291]

Hi - in my case the formula that was identified as critical was changing the colour of a cell.

Like reported above, the exclusions are not visible for me but my understanding was that only the ones in the image  below (taken from the documentation) could be excluded i.e. i dont see "Fix high severity formula issues"

Thanks for response