{"id":1664,"date":"2026-09-15T08:26:50","date_gmt":"2026-09-15T13:26:50","guid":{"rendered":"https:\/\/automatethemundane.com\/index.php\/2026\/09\/15\/automatic-code-review-of-power-platform-canvas-app-reviews-2\/"},"modified":"2026-09-15T08:32:08","modified_gmt":"2026-09-15T13:32:08","slug":"automatic-code-review-of-power-platform-canvas-app-reviews-2","status":"publish","type":"post","link":"https:\/\/automatethemundane.com\/index.php\/2026\/09\/15\/automatic-code-review-of-power-platform-canvas-app-reviews-2\/","title":{"rendered":"Automatic Code Review of Power Platform Canvas App Reviews"},"content":{"rendered":"\n

A few weeks ago, I was reading on some strategies to do \u201ccode\u201d reviews for power platform solutions. My goal was to figure how to review a solution that was being pushed via Power Platform Pipelines and give the developer and project lead a scoring for how it performed. This got me reading more into Power Apps Code Review tool created by Power CAT powerapps-tools\/Tools\/Apps\/Microsoft.PowerApps.CodeReview at master \u00b7 microsoft\/powerapps-tools \u00b7 GitHub<\/a>. This provided a framework for getting Canvas apps reviewed and ranked but wanted to automate the reviews so that it would do the review as it was being promoted in the pipeline. <\/p>\n\n\n\n

The basic architecture will be like this\n<\/p>\n\n\n\n

\n\n\nflowchart TD\n\tsubgraph Tennant\n\tB[1.2.1 - Start App Review] --> |Solution Name & Solution Version & Canvas App Score & Link to Report| C\n\tdirection TB\n subgraph Pipeline Orchestrator\n A[1.2 - When a push to test happens] -->|Solution Name & Solution Version & Stage Run ID & ArtifactID| B\n end\n subgraph Production\n C[Solution History Table]\n end\n end\n\n\n<\/div>\n\n\n\n

When a new push to test occurs, a review of the solution will occur. After the review, the output is sent to the PPPM Solution History table. From here we can add the score to the notification sent to the project lead before approving the solution into production. <\/p>\n\n\n\n

Solution History Table<\/h2>\n\n\n\n

Within the PPPM solution, create a new table called Power Platform Solutions History<\/p>\n\n\n\n

<\/p>\n\n\n\n

\nerDiagram\nSolution_History}| -- || PPPM_Solution_Tracking:contains\n Solution_History {\n string Solution_Version_Name PK\n url Link_to_report\n float App_Review_Score\n float Review_Score\n GUID PPPM_Solution FK\n }\n\n<\/div>\n\n\n\n
\"\"\/<\/figure>\n\n\n\n

Power Apps Code Review Tool<\/h2>\n\n\n\n

The Power Apps Code Review tool is comprised of two apps (MDA and a canvas). The MDA is where all the rules and the reviews can be reviewed. The canvas app is where the an amazing showcase for what a canvas app can do. It provides a great interface for Code Reviews Checklists, App Checker, App Overview, Code Review, and Review Results<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n
\"\"\/<\/figure>\n\n\n\n
\"\"\/<\/figure>\n\n\n\n
\"\"\/<\/figure>\n\n\n\n
\"\"\/<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Within the app I made an update to help with deep linking. <\/p>\n\n\n\n

    \n
  1. Within the AppOnStart I set the AppID to the environment variable the equals the environment variable andy_PowerAppsReviewAppID\n
      \n
    1. \"\"<\/figure><\/li>\n\n\n\n
    2. Set(
      AppID,
      LookUp('Environment Variable Values', 'Schema Name' = \"andy_PowerAppsReviewAppID\").Value
      );<\/code><\/li>\n<\/ol>\n<\/li>\n\n\n\n
    3. Within the AppStartScreen I updated the If statement to navigate to the SolutionDetailsScreen\n
        \n
      1. \"\"<\/figure><\/li>\n\n\n\n
      2. If(!IsBlank(Param(\"reviewid\")), SolutionDetailsScreen)<\/code><\/li>\n<\/ol>\n<\/li>\n\n\n\n
      3. Within the OnVisible of the SolutionDetailsScreen, add an if statement that will set the variable ActiveSolutionReviewID to be either reviewid or SolutionReviewID. Then update the var SelectedSolutionReview and collection SolutionReviewApps.\n
          \n
        1. \/\/ Set ActiveSolutionReviewID based on whether the parameter is blank
          Set(
          ActiveSolutionReviewID,
          If(
          IsBlank(Param(\"reviewid\")),
          SolutionReviewID,
          Param(\"reviewid\")
          )
          );

          \/\/ Set SelectedSolutionReview using ActiveSolutionReviewID
          Set(
          SelectedSolutionReview,
          LookUp(
          PatchedSolutionReviews,
          Rev_SolutionReview = GUID(ActiveSolutionReviewID)
          )
          );

          \/\/ Populate SolutionReviewApps using ActiveSolutionReviewID
          ClearCollect(
          SolutionReviewApps,
          Filter(
          Rev_Apps,
          Rev_Apps_SolutionReview.Rev_SolutionReview = GUID(ActiveSolutionReviewID) &&
          Chx_AppType <> AppType.'Model Driven App'
          )
          );
          <\/code><\/li>\n<\/ol>\n<\/li>\n\n\n\n
        2. The Solution score button in the upper right needs to be updated as well to use the new variable\n
            \n
          1. \"\"<\/figure><\/li>\n\n\n\n
          2. Round(
            LookUp(
            Rev_SolutionReview,
            Rev_SolutionReview = GUID(ActiveSolutionReviewID)
            ).Nb_SolutionScore * 100,
            0
            ) & \"%\"<\/code><\/li>\n<\/ol>\n<\/li>\n\n\n\n
          3. I also updated the header back button to be hidden if the review is not blank. This way the user can only navigate to the report they were sent.\n
              \n
            1. \"\"<\/figure><\/li>\n<\/ol>\n<\/li>\n<\/ol>\n\n\n\n

              Pipeline Flow Configuration<\/h2>\n\n\n\n

              1.2 - When a push to test happens<\/h3>\n\n\n\n

              The trigger for the flow will be When an action is performed<\/p>\n\n\n\n

              \"\"\/<\/figure>\n\n\n\n

              To ensure that the trigger only occurs when a push to test occurs, a trigger condition needs to be set. For me, it is the deploy to test stage<\/p>\n\n\n\n

              \"\"\/<\/figure>\n\n\n\n
              @equals(triggerOutputs()?['body\/OutputParameters\/DeploymentStageName'], 'STAGENAME')<\/code><\/pre>\n\n\n\n
              Next will be a Scope with two Dataverse Get row ID actions<\/p>\n\n\n\n
              \"\"\/<\/figure>\n\n\n\n
              <\/p>\n\n\n\n
              The first will get the stage run information using the stage run id from the trigger<\/p>\n\n\n\n
              triggerOutputs()?['body\/InputParameters\/StageRunId']<\/code><\/pre>\n\n\n\n
              \"\"\/<\/figure>\n\n\n\n
              <\/p>\n\n\n\n
              The other will get the Deployment Artifact from the action above<\/p>\n\n\n\n
              outputs('Get_a_row_by_ID_-_Deployment_Stage_Runs')?['body\/_artifactid_value']<\/code><\/pre>\n\n\n\n
              <\/p>\n\n\n\n
              \"\"\/<\/figure>\n\n\n\n
              A child flow will be triggered that starts the actual app review<\/p>\n\n\n\n
              <\/p>\n\n\n\n
              \"\"\/<\/figure>\n\n\n\n
              <\/p>\n\n\n\n
              \"\"\/<\/figure>\n\n\n\n
              A scope with a condition based on the review status of the app review<\/p>\n\n\n\n
              <\/p>\n\n\n\n
              \"\"\/<\/figure>\n\n\n\n
              \"\"\/<\/figure>\n\n\n\n
              Within the True side, add two Dataverse Actions. <\/p>\n\n\n\n
              <\/p>\n\n\n\n
              \"\"\/<\/figure>\n\n\n\n
              The first will get the GUID of the solutions tracking table in the production environment using the name of the Artifact<\/p>\n\n\n\n
              <\/p>\n\n\n\n
              \"\"\/<\/figure>\n\n\n\n
              The second adds a row to the Solution History table in Production table<\/p>\n\n\n\n
              \"\"\/<\/figure>\n\n\n\n
              <\/p>\n\n\n\n
              1.2.1 - Start App Review<\/h3>\n\n\n\n
              The 1.2.1 flow is the child flow called from the 1.2.1 flow and start the actual app review<\/p>\n\n\n\n
                \n
              1. The trigger will be a manual trigger that asks for the StageRunID, ArtifactID, ArtifactName, ArtifactVersion\n
                  \n
                1. \"\"<\/figure><\/li>\n<\/ol>\n<\/li>\n\n\n\n
                2. Next, add a Boolean variable called varStatus\n
                    \n
                  1. \"\"<\/figure><\/li>\n<\/ol>\n<\/li>\n\n\n\n
                  2. To get the artifact out of the pipeline a HTTP action\n
                      \n
                    1. \"\"<\/figure><\/li>\n<\/ol>\n<\/li>\n\n\n\n
                    2. Within a Scope action four Dataverse Actions are added\n
                        \n
                      1. \"\"<\/figure><\/li>\n<\/ol>\n<\/li>\n\n\n\n
                      2. The first will add a new row to the Solution Review table\n
                          \n
                        1. \"\"<\/figure><\/li>\n<\/ol>\n<\/li>\n\n\n\n
                        2. The second will upload the file to the Solution Review table\n
                            \n
                          1. \"\"<\/figure><\/li>\n<\/ol>\n<\/li>\n\n\n\n
                          2. The third adds a new row to the Review Request table\n
                              \n
                            1. \"\"<\/figure><\/li>\n<\/ol>\n<\/li>\n\n\n\n
                            2. The fourth will set the review status of In Progress\n
                                \n
                              1. \"\"<\/figure><\/li>\n<\/ol>\n<\/li>\n\n\n\n
                              2. After the Scope another scope is added with a Do Until Action and a Dataverse Action\n
                                  \n
                                1. \"\"<\/figure><\/li>\n<\/ol>\n<\/li>\n\n\n\n
                                2. The Do until will keep running until varStatus is equal to true\n
                                    \n
                                  1. \"\"<\/figure><\/li>\n\n\n\n
                                  2. Within the Do until add a delay action, this will give the review time to run<\/li>\n\n\n\n
                                  3. Next add a Get row by ID of the Solution Review table\n
                                      \n
                                    1. \"\"<\/figure><\/li>\n<\/ol>\n<\/li>\n\n\n\n
                                    2. Add a condition that checks to see if the status of the review is done\n
                                        \n
                                      1. \"\"<\/figure><\/li>\n<\/ol>\n<\/li>\n\n\n\n
                                      2. If it equals Done or Error and not In Progress then it will set the variable varStatus to true\n
                                          \n
                                        1. \"\"<\/figure><\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n\n\n\n
                                        2. The last action within the scope will get the Solution Review record via ID\n
                                            \n
                                          1. \"\"<\/figure><\/li>\n<\/ol>\n<\/li>\n\n\n\n
                                          2. The last action within the flow will be to respond to the parent flow with the app review score, the review status, and the reviewid<\/li>\n<\/ol>\n\n\n\n
                                            \"\"\/<\/figure>\n\n\n\n
                                            <\/p>\n\n\n\n
                                            \n\n\n\n
                                            This was a really interesting post to write. I have always wanted to do \u201creviews\u201d with my teams that do not have ADO or another connected system. In the next post, I will go over how I build a method for doing reviews on Power Automate flows using Power Platform Pipelines.  <\/p>\n","protected":false},"excerpt":{"rendered":"
                                            A few weeks ago, I was reading on some strategies to do \u201ccode\u201d reviews for power platform solutions. My goal was to figure how to review a solution that was being pushed via Power Platform Pipelines and give the developer and project lead a scoring for how it performed. This got me reading more into […]<\/p>\n","protected":false},"author":1,"featured_media":1665,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,22,30,42,45,37,35],"tags":[],"class_list":["post-1664","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-canvas-app","category-dataverse","category-power-automate","category-power-pipelines","category-pppm","category-security","category-tables","entry","has-media"],"jetpack_featured_media_url":"https:\/\/automatethemundane.com\/wp-content\/uploads\/2026\/09\/Automatic-Code-Review-of-Power-Platform-Canvas-App-Reviews-scaled.jpg","_links":{"self":[{"href":"https:\/\/automatethemundane.com\/index.php\/wp-json\/wp\/v2\/posts\/1664","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/automatethemundane.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/automatethemundane.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/automatethemundane.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/automatethemundane.com\/index.php\/wp-json\/wp\/v2\/comments?post=1664"}],"version-history":[{"count":4,"href":"https:\/\/automatethemundane.com\/index.php\/wp-json\/wp\/v2\/posts\/1664\/revisions"}],"predecessor-version":[{"id":1669,"href":"https:\/\/automatethemundane.com\/index.php\/wp-json\/wp\/v2\/posts\/1664\/revisions\/1669"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/automatethemundane.com\/index.php\/wp-json\/wp\/v2\/media\/1665"}],"wp:attachment":[{"href":"https:\/\/automatethemundane.com\/index.php\/wp-json\/wp\/v2\/media?parent=1664"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/automatethemundane.com\/index.php\/wp-json\/wp\/v2\/categories?post=1664"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/automatethemundane.com\/index.php\/wp-json\/wp\/v2\/tags?post=1664"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}