Identify deprecated JS code in your Power Platform solution using Solution Checker

Recently, you must’ve received an intimation from Microsoft saying that ODATA v2 is now deprecated. See this link: https://powerapps.microsoft.com/en-us/blog/odata-v2-0-service-removal-date-announcement/

And if you are wondering how to go about finding what has been used, you can use Solution Checker to identify deprecated code which should show up like below using your Solution Checker.

Let’s see how we can use Solution Checker!

Running Solution Checker

Here’s how you can run Solution Checker in Power Apps Maker Portal (https://make.powerapps.com/) and see the results –

  1. Given that your solution already contains the JS Web Resources which you want to run Solution Checker on, you can select the Solution and expand Solution Checker to click Run as shown below.

  2. It takes a few moments to Run the Solution Checker solution. You’ll see the spinner as shown below.

  3. Once completed, you can expand the Solution checker and click on View Results.

  4. Once you click on View Results, you’ll see the list of detected anomalies in your JS Web Resources.
    Apart from the suggested JS best practices, you can see the Category Upgrade Readiness to identify the deprecated code being used in your solutions.

  5. Once you click on the Reference link in each of these results, it’ll open up a Pane on the right hand side to show what the issue is

  6. And when you click on Get the complete guide, here’s the link of the same (https://learn.microsoft.com/en-gb/power-apps/maker/data-platform/powerapps-checker/rules/web/avoid-2011-api?WT.mc_id=DX-MVP-5003911) which will give you the below details in Microsoft Learn Documentation –

  7. Now, if you look at the code that is being references in the Solution Checker result, you’ll see the old code (marked with Red Box)being used.
    Instead, you should use the new code (marked with Green Box) to do carry out the newer version of the functionality –

  8. See the next section in this blog to get the details on the deprecation in client side scripting for Power Platform / Dynamics 365 CRM.

Important Deprecations for Power Apps & Power Automate

Here’ are the Deprecated APIs for Power Platform / Dynamics 365 CRM Client Scripting: https://learn.microsoft.com/en-us/power-platform/important-changes-coming#some-client-apis-are-deprecated?WT.mc_id=DX-MVP-5003911

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Select the item based on a key value using Filter Array in Power Automate
  2. Select values from an array using Select action in a Power Automate Flow
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate
Advertisement

Power Platform self-service analytics Data Export to Data Lake [Preview] | Power Platform Admin Center

Now, you can also export the Analytics Data to Azure Data Lake in order to further extend the derive rich data analytics!
At the time of writing this post, this feature is in Preview (As you’ll also see from the screenshots below)

This is a great feature where you can extract this Data into Data Lake and then further enrich and derive rich Power BI reporting based on your use-case.

In case you are new to understanding Azure Data Lake and pricing, you can review this – https://azure.microsoft.com/en-gb/solutions/data-lake/?WT.mc_id=DX-MVP-5003911

Data Export (Preview)

In Power Platform Admin Center (https://admin.powerplatform.microsoft.com/), here’s how you can setup Data Export –

  1. Navigate to Data Export in Power Platform Admin Center given that you have appropriate rights –


  2. Then, you’ll get to choose amongst the Power Apps or Power Automate data to be exported to Data Lake.

  3. In this example, I’ll choose Power Automate. As I select Power Automate, you’ll see that Tenant-Level Analytics are required and hence, already considered as Yes. If not, you’ll need to Enable Tenant-Level Analytics while doing this step – Here’s another post on how to Enable and Use Tenant Level Analytics –


  4. Now, In the next section you’ll need to choose the Subscription.


  5. Further, select the Resource Group and eventually, the Storage Account as well.


    And Storage Account is selected as well.

  6. Once everything looks good, you can click on Create.

  7. In a few moments, this will appear in Data Lake section of the Data Export. It will take up to 24 hours for the data to first start showing in Data Lake.

  8. Once this is completed after about 24 hours, you’ll see the status of the Data Lake data package changed to connected.


Data Export to Data Lake

Let’s look at the Azure Storage Explorer to connect to our Data Lake and see the Power Platform data – In case you are looking to install Azure Storage Explorer, here’s a post – Microsoft Azure Storage Explorer | Getting Started

  1. Once authenticated to the correct environment in Azure Storage Explorer, here’s what you would see in the ADLS Gen 2 (In case you want to create ADLS Gen 2 storage account, you can review this post – Create ADLS Gen 2 Storage Account for Azure Data Lake)
    You’ll see powerplatform folder show up.

  2. If you open this folder, since we had chosen Power Automate, it’s folder will be created.

  3. And let’s go in Flows folder to see the data. You’ll find json files of the same. You can double click to open it and it’ll open in whatever editor you have installed.

  4. In this case, I had VS Code, so here’s what the Flow data looks like –

  5. Likewise, you can dig deeper in this data and use this further for your reporting!

Here’s Microsoft Learn Document on the same – https://learn.microsoft.com/en-us/power-platform/admin/self-service-analytics?WT.mc_id=DX-MVP-5003911

Here’s Microsoft Learn Docs for Tenant-Level Analytics – https://learn.microsoft.com/en-gb/power-platform/admin/tenant-level-analytics#how-do-i-enable-tenant-level-analytics?WT.mc_id=DX-MVP-5003911

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Select the item based on a key value using Filter Array in Power Automate
  2. Select values from an array using Select action in a Power Automate Flow
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform\
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Custom Pages in Power Platform and adding them in Model-Driven Apps | Power Apps

You Can create Custom Pages in as a Canvas App and add it to Model Driven App! Here’s a quick tutorial on how you can do this!

Creating Custom Pages

Here’s how you can create Custom Pages. Make sure you are in Power Apps and in the correct intended environment (https://make.powerapps.com/) –

  1. Make sure you are inside a Solution.

  2. Now, you can drop down from the + New menu and expand App. Then, you’ll find Page as an option which is different from Canvas App.

  3. When you click on Page, you’ll get the Canvas App Studio with the capabilities of Canvas App to be added to your Page.

  4. Now, let’s say you have designed the Page to serve your desired purpose. Make sure you Save and Publish the App, it’ll ask you to Enter the Name for the App (or rather, Page)


    Enter a suitable name and click on Save.

  5. Once Saved, make sure to Publish again and confirm the Publish just like you would do for a Canvas App.


    And confirm the Publish action.

  6. Now once this is done, you can go back to the Solution and check that the Page will appear.


    and that’s how you have created a Page. Now, let’s consume this in your Model-Driven App!

Adding Custom Pages to Model-Driven Apps

Now, in the same solution, I’ll add the Model-Driven App so that I can configure the new Page I created in this Model-Driven App –

  1. When I go into App section in the solution I’m working in.

  2. And in that, I can click on Add existing button and expand App and then select Model-Driven App

  3. Now, from all the Apps, I want to add this Custom Page to the Sales Hub App. It could be anything else in your case.

  4. Once added, open the App.

  5. Once opened, you’ll see the + Add Page button. Click it.

  6. Now, the Dialog will ask what type of Page should be added. Custom Page is to be selected here.

  7. Now, you will be given option to either Create New (which we could have done directly but I wanted to demonstrate how to create within the Solution itself first), or add Existing.
    We’ll choose to add Existing Custom Page. And then, we select the Custom Page we just created i.e. Account Review Page.
    For the Page to show in the Site Map, make sure Show in navigation is ticked.


  8. Once you Add, you’ll see how the Page appears in the Model-Driven App. Publish your changes to this Model-Driven app is you are satisfactory.


  9. Once this is done, your Custom Page is added to the Model-Driven App and here’s how it looks!

Here’s complete document on Custom Pages on Microsoft Learn – https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/model-app-page-overview?WT.mc_id=DX-MVP-5003911

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Select the item based on a key value using Filter Array in Power Automate
  2. Select values from an array using Select action in a Power Automate Flow
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform\
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Set up Power Platform Tools in Visual Studio Code | Power Platform CLI

In your Visual Studio Code, you can now set up Power Platform Tools / Power Platform CLI Extension for Visual Studio Code (VS Code).

Here’s VS Marketplace Link for Power Platform Tools – https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.powerplatform-vscode

Let’s review in this post!

Extensions in Visual Studio Code

Here’s how you can install Power Platform Build Tools in Visual Studio Code

  1. Navigate to Extensions section in Visual Studio Code.

  2. Search for Power Platform Tools

  3. It’ll then start installing –

  4. When you open the installed extension, you’ll be asked to Add Auth Profile.

  5. Clicking on Add Auth Profile will open up the Login dialog.

  6. Once you enter Username and Password and authenticate yourself into the environment, after a few moments, you’ll see the environments show up in Visual Studio Code.

  7. And if you expand on the environments, you’ll see the Solutions in the environment and each of them will let you get some information right away –



Testing Power Platform Tools Extension

Let’s make sure the Power Platform Tools were successfully installed –

  1. Once installed, you can open a new Terminal and type ‘pac


  2. It should show you all the Commands available since you are logged in.

  3. And as you start to use the Commands, they have other options inside the Menus themselves.


  4. Here’s a sample Command I used to see all the Environments

  5. Had Power Platform Tools not been installed or Disabled, you’d see the below error –

Here’s the reference Blog which talks about Power Platform Extension for VS Code – https://powerapps.microsoft.com/en-us/blog/power-platform-extension-for-vs-code/

Here are some Power Automate posts you want to check out –

  1. Select the item based on a key value using Filter Array in Power Automate
  2. Select values from an array using Select action in a Power Automate Flow
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform\
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Using Environment Variables in Power Automate and Canvas Apps

Here’s how you can use Environment Variables in your environment in Power Automate and Canvas Apps!

In case you are looking to create Environment Variables, here’s the post: Environment Variables in Power Apps and Power Automate

Power Automate

Here’s how you can use Environment Variables in a Flow –

  1. You can’t use/access Environment Variables in a Flow which is not in a solution –
    Environment Variables are accessible in the Dynamic Content section on the very top of the list. [Since the below Flow is outside a Solution, you can’t see the Environment Variables]

  2. Now, this Flow is within a Solution –

  3. And then you access the Dynamic Content, you can see the Environment Variables.

  4. And when you Run the Flow, the Environment Variable will show the value based on the Data Type set for the variable at appropriate places –

Canvas Apps

Unlike Power Automate Flow, Environment Variables in Canvas Apps can be utilized even if the Canvas App was created outside a solution –

  1. In a Canvas App, click to Add Data Source.

  2. On the Environment Variable Definitions/Values is added to the Canvas App as Data Sources, let’s take a simple Text control to read the Value from the Environment Variable used in the above Flow example –
    I’ll use Lookup() function in Power Automate to fetch the value of the Environment Variable by it’s Schema Name
    Even if you only added Environment Variable Values table as Data Source, the Environment Variable Definition too will be added once you use the Lookup() function to fetch the value.

Hope this was useful!

Here are some Power Automate posts you want to check out –

  1. Environment Variables in Power Apps and Power Automate
  2. Select the item based on a key value using Filter Array in Power Automate
  3. Select values from an array using Select action in a Power Automate Flow
  4. Blocking Attachment Extensions in Dynamics 365 CRM
  5. Upgrade Dataverse for Teams Environment to Dataverse Environment
  6. Showing Sandbox or Non Production Apps in Power App mobile app
  7. Create a Power Apps Per User Plan Trial | Dataverse environment
  8. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  9. Co-presence in Power Automate | Multiple users working on a Flow
  10. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  11. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  12. Call a Flow from Canvas Power App and get back response | Power Platform\
  13. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  14. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  15. Asynchronous HTTP Response from a Flow | Power Automate
  16. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  17. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Environment Variables in Power Apps and Power Automate

Here’s how you can create Environment Variables in Power Apps or Power Automate portal.

Creating Environment Variable in a Solution

First, create Solution to store your environment variable.

  1. In this example, I’m using Power Apps (https://make.powerapps.com/) to create a n Environment Variable.
    In the Solution, I can click on New and then look for an Environment variable.

  2. Below are the types of Environment variables which you can create –


  3. For example, I’m storing the current Org’s ID in an Environment Variable which I want to re-use in my Flow for whatever purpose (Just an example 🙂).
    I’ve given it a suitable name and stored the current value as well.

  4. And my Environment Variable will be created in a Solution in either Power Apps or Power Automate.

  5. Now that your Environment variable is ready, you can feel free to use it in Power Automate and Power Apps. Environment variables can be used in Flows and Canvas Apps which are in a solution.
    Here’s how you can use Environment Variables in Canvas Apps and Flow – Using Environment Variables in Power Automate and Canvas Apps

You can look at Microsoft’s Documentation on Environment Variables for more info – https://learn.microsoft.com/en-us/power-apps/maker/data-platform/environmentvariables?WT.mc_id=DX-MVP-5003911

Hope this was useful!

Here are some Power Automate posts you want to check out –

  1. Select the item based on a key value using Filter Array in Power Automate
  2. Select values from an array using Select action in a Power Automate Flow
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform\
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Power Platform URLs

If you are having a hard-time keeping track of what URLs to enter / bookmark for everything that you do in Power Platform / Dynamics 365, here’s a post to help you pick and store URLs from the get go

I already have a post where you can find all the Admin Center URLs- Admin Center URLs under M365 – Power Platform, Teams, SharePoint, Power BI

Power Automate

Power Automate URL is being changed from https://flow.microsoft.com/ to https://make.powerautomate.com/ to line up consistently with Power Apps maker environment –
Here’s what you’ll see when you are in Power Automate (you can also see the notification on the top in the screenshot below regarding this change) –

Power Apps

In order to see all the Canvas / Model-Driven Apps, you can navigate to this URL: https://make.powerapps.com/
You’ll be landed here –

Power BI

Once you have the appropriate Power BI license assigned to your user, you can visit Power BI Home using this URL: https://app.powerbi.com/home

Hope this was useful!

Here are some Power Automate posts you want to check out –

  1. Blocking Attachment Extensions in Dynamics 365 CRM
  2. Upgrade Dataverse for Teams Environment to Dataverse Environment
  3. Showing Sandbox or Non Production Apps in Power App mobile app
  4. Create a Power Apps Per User Plan Trial | Dataverse environment
  5. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  6. Co-presence in Power Automate | Multiple users working on a Flow
  7. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  8. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  9. Call a Flow from Canvas Power App and get back response | Power Platform\
  10. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  11. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  12. Asynchronous HTTP Response from a Flow | Power Automate
  13. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  14. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Show only configured Activities Related records section | Power Platform Admin Center

Here’s a setting which I personally don’t think would matter much and I’ll get to why I think like that.

Show Activities only configured in the App

Let’s navigate to the Settings for the organization in the Power Platform Admin Center (https://admin.powerplatform.microsoft.com) –

  1. Click on Settings once you are in the environment which you want to configure this feature.

  2. In Settings, go to Features.

  3. In Features, you can scroll to the bottom and see this option.

  4. What this Turned Off feature does is show all the Activities in the (example: Sales Hub) App -> Related section of the records’ + New Activity button


    And the + New Activity button in the Activities Associated View will show all the Activities by default regardless if they are configured in the App or not.

  5. However, the gripe is that this doesn’t reflect in the Timeline control by default. You have to change the options in the Timeline control separately. (And the Timeline is the most common way you would create an Activity, right?)

  6. Now, let’s turn this setting On and see the effect.

Turned On

Now, when this is turned on, the Activities’ Associated View’s + New Activity button will only show the Activities which are included in the App itself and not all.

I wished this was also reflected easily on the Timeline control and in the Main Activity View as well from it’s own entity in the SiteMap. Perhaps it could be work in progress. I’ll clarify once I know more! 😊

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Showing Sandbox or Non Production Apps in Power App mobile app
  2. Create a Power Apps Per User Plan Trial | Dataverse environment
  3. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  4. Co-presence in Power Automate | Multiple users working on a Flow
  5. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  6. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  7. Call a Flow from Canvas Power App and get back response | Power Platform\
  8. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  9. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  10. Asynchronous HTTP Response from a Flow | Power Automate
  11. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  12. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Comments in Power Platform [Preview] | Power Automate example

Here’s a new feature across Power Platform stack i.e. Power Apps / Power Virtual Agents and Power Automate

Comments

Let’s consider an example of a Flow / Power Automate for the Comments

  1. In a Cloud Flow, now you’ll see a Comments (preview) show up.

  2. When you click on it, Comments pane will open up letting you add Comments to the Flow.

  3. And just like in Word, you’ll be able to enter comments for the Flow. These comments are added pertaining to the selected Flow Step or the first Flow Step by default.
    Click on the send button to add the comment.

  4. Now, once a comment is added, a counter/badge of count of comments will appear on the Step the comment is tied to.

  5. As you proceed, multiple users can add their comments to different steps. (Ideally, since I added 2 comments to the second step, both should be highlighted. This could be in preview and in the works). I’ll update this space again as I have more info

  6. Similarly, a thread looks like the one highlighted on the right and if you notice, the Flow Step too will lit up a little to denote which step the comment thread belongs to.
    Also, a comment thread is treated as count of 1.

  7. For each thread, you have the below options per thread/comment.

  8. And if you Resolve a comment/thread, notice that the counter from the Flow Step is discounted/removed and the comment thread is marked with Resolved tag on the top.

    Also, the step it belongs to is highlighted a little and is slightly difficult to identify right away
    Perhaps this behavior could be changed in the future once in GA.


  9. Once a thread is Resolved, it could be Reopened or Deleted as the icons suggest.

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Showing Sandbox or Non Production Apps in Power App mobile app
  2. Create a Power Apps Per User Plan Trial | Dataverse environment
  3. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  4. Co-presence in Power Automate | Multiple users working on a Flow
  5. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  6. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  7. Call a Flow from Canvas Power App and get back response | Power Platform\
  8. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  9. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  10. Asynchronous HTTP Response from a Flow | Power Automate
  11. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  12. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Performance Insights for Model-Driven Apps | [Preview]

One of the important aspects of ‘User Adoption’ is also ensure that the Model-Driven App you’ve designed for your Org’s Users stays optimized and ensures the users get the best of it.

Let’s see how we can utilize Performance Insights to help us optimize our Model-Driven App!

Performance (Preview)

Performance Insights is in Preview and here’s how you can access the same.

  1. Go to https://make.powerapps.com/

  2. Now, in your Apps below, select the Model-Driven App you want to view Performance metrics of.


  3. Now, once you open, you’ll see the metrics as below


    Let’s understand how you can read these metrics and take actionable actions on the same.


Understanding the Insights

These insights are categorized based on severity. Let’s see which needs your attention the most –

  1. The Insights can be narrowed based on the timeframe of 24 hours, Unfortunately, I have only 1 Date to show in my case.


  2. I recommend paying special attention to the ones with Warning on them


  3. Now, looking at the first one for example is PluginTraceLog which I left ON while I was working on Plugins on this environment in the App.
    So, if I select the first one


    The right hand pane will detail out what the issue is and what Area to focus on.



  4. Also, if you look at the How to improve part, it’ll point you to the Microsoft Docs for the suggested workaround/action.


    It’ll take you to the Microsoft Docs section of the particular issue in question –


  5. In case you have a new environment and didn’t work inside the App significantly for a particular time frame, you’ll see this message.



    Here’s the complete Microsoft Docs article on the detailed Performance Insights for Model-Driven Apps –
    https://docs.microsoft.com/en-us/powerapps/maker/common/performance-insights-overview?WT.mc_id=DX-MVP-5003911

Here are some more Model-Driven and Canvas Power Apps posts you might want to check out –

  1. HTML Text control in Canvas Power Apps | Power Platform
  2. Disable Recent Records from Dynamics 365 Lookup Control | Model-Driven Apps [Quick Tip]
  3. Advanced Lookup in Model-Driven Apps | Power Platform
  4. New App Designer for Model-Driven Apps | Power Platform
  5. Rich Text Control for Canvas and Model-Driven App | Quick Tip
  6. Form Access Checker in new Power Apps Form Designer | Model-Driven Apps in Dynamics 365
  7. How to add Rating Values to Rating Models in D365 Field Service and PSA
  8. Log Canvas Power App telemetry data in Azure Application Insights | Power Apps
  9. Transition effect on Gallery Items when hovered over in a Canvas Power App | [Quick Tip]
  10. Retrieve Hashtags from Text in a Canvas Power App | Power Platform

Thank you!