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

March 15, 2023 priyeshwagh777 Power Platform, Power Platform Admin Center deprecated javascript, odata v2, solution checker, solution in power platform

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 –

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.
It takes a few moments to Run the Solution Checker solution. You’ll see the spinner as shown below.
Once completed, you can expand the Solution checker and click on View Results.
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.
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
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 –
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 –
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 –

Power Apps Developer Plan environments | Power Platform

February 22, 2023 priyeshwagh777 Microsoft PowerApps, Power Platform Admin Center developer environment for power apps, developer type environment in dataverse, power apps developer plan

Developers can now have Environments of their own to test and review Power Apps / Power Automate etc. Here’s how you can get yours!

Learn More about Power Apps Developer: https://learn.microsoft.com/en-us/power-apps/maker/developer-plan?WT.mc_id=DX-MVP-5003911

If you are looking to Sign Up for the Developer Plan, you can use this Link: https://powerapps.microsoft.com/en-us/developerplan/?WT.mc_id=DX-MVP-5003911

Create Developer Environment

Given that you are Power Platform Admin Center, you can create a new Environment like so –

Go to Power Platform Admin Center and then Environments (https://admin.powerplatform.microsoft.com/environments). Click on + New to create a new Environment.

And then you can select the Type
Now, can you check what URL you want to provide and then click on Finish
Then, your environment will be initiated for creation like any other Environment. Notice the type is Developer.
Once created, if you go in the Environment, you can click the Edit to review the Settings for this Environment.
And you can see that the Security Group cannot be added to this Environment.

User’s Environment

If a User wants to create their own environment under the Power App Developer Plan (https://powerapps.microsoft.com/en-us/developerplan/?WT.mc_id=DX-MVP-5003911), they can go to the Homepage of the Power Apps Developer plan and click on Existing User? Add a dev environment >
Then, you can enter your credentials and you’ll see this page.
Once this is provisioned, you’ll be taken to your Environment and I’ll look like below –
And in the Power Platform Admin Center, the Admins can see that the Environment has been created of Type Developer by SYSTEM.

Hope this helps!

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

Thank you!

Weekly Digest for usage insights | Power Platform Admin Center

February 7, 2023 priyeshwagh777 Power Platform Admin Center Power Platform Admin Center, power platform admin center weekly digest, weekly digest

One of the features in Power Platform Admin Center is that now you can receive Weekly Updates in the form of a Newsletter for the Managed Environments.

Pre-Requisites

Below are the Pre-requisites for enabling Weekly Digest

Tenant-Level Analytics must be enabled in your Power Platform Tenant. Here’s a post to see how you can enable Tenant-Level Analytics – Tenant-Level Analytics in Power Platform Admin Center | For Power Apps and Power Automate
Only Managed Environments Updates are available – Here’s how you can learn more about Managed Environments – Enable Managed Environments in Power Platform Admin Center
Under those Managed Environments, only those Managed Environments will be considered which have been enabled for Weekly Digest. While enabling Managed Environments in the above step #2, ensure this checkbox is marked in order to consider the Managed Environment for Weekly Digest –

Enable Weekly Digest

Given the above Pre-requisites are met, here’s how you can enable Weekly Digest –

Navigate to Tenant Settings in the Power Platform Admin Center (https://admin.powerplatform.microsoft.com/tenantsettings) – Look for Weekly digest. Notice that it is marked with a green icon which indicates that it will only be applicable for Managed Environments.
On the right hand side, you’ll see place to enter email addresses (separated by semicolons) who should receive the Weekly Digest emails.
Power Platform Administrators and Dynamics 365 Administrators only will receive these updates.
Once you entered the email addresses, you can Save those and you’ll see the below message upon confirmation.
That’s it!
And then on a Monday, I saw this in my mailbox!

Hope this helps!

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

Thank you!

Enable Early Access Wave 1 2023 | Power Platform

February 6, 2023 priyeshwagh777 Power Platform Admin Center early access, enable early access, power apps, Power Platform

Like every 6 months, enabling Early Access is one of the best things to look forward to as Microsoft announces Release Plans! So, here’s how you can enable Early Access for Wave 1 2023 if you are new to managing Power Platform environments!

It is recommended to enable Early Access features only for Sandbox environments as it is not GA [General Availability] yet.

Power Platform Admin Center

Given that you are a Power Platform Administrator / Dynamics 365 Administrator, here’s how you can enable Wave 1 2023 access for your Sandbox environment –

Select the Sandbox environment
Then, see the Updates section where you’ll now see 2021 Wave 1 updates available in Off mode.
On the right hand side, you can select the U
Then, enter the Display Name of the environment correctly in order to ensure you are enabling this on the correct environment.
Once you confirm, you’ll see that the Updates have started applying in the background.
And when you click or refresh, you’ll see what’s being Activated in the background based on how your environment is set up.
It takes a few hours based on the environment for the Wave 1 2023 Updates to be applied.

And you’re set! Here’s Microsoft Learn Documentation for Wave 1 2023 for Power Platform / Dynamics 365: https://learn.microsoft.com/en-us/dynamics365/release-plans/?WT.mc_id=DX-MVP-5003911

Hope this helps!

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

Thank you!

Enable Managed Environments in Power Platform Admin Center

January 31, 2023 priyeshwagh777 Power Platform Admin Center managed environments, managed environments in power platform admin center, Power Platform Admin Center

Here’s what Managed Environments do! They provide more control on how you administer the Environments i.e. by limiting App Sharing, applying Data Policies on the environment and even how Solution Checker should allow to import solutions upon detecting critical issues (Solution Checker feature for Managed Environments is in Preview at the time of writing this post!).

Below is the snipped from Microsoft Learn Document highlighting the capabilities of Managed Environments

Further, as I explore these features more, I’ll update and add links to the posts explaining each of the features in details.

Enable Managed Environments in Power Platform Admin Center

Given that you have appropriate permissions to take administrative actions on Power Platform environments, you can navigate to Power Platform Admin Center and then in Environments (https://admin.powerplatform.microsoft.com/environments) –

Select an Environment and click on the ellipses on the menu.
Once you select the same, review the License implications as highlighted below –
Here’s the Microsoft Documentation on the same – https://learn.microsoft.com/en-gb/power-platform/admin/managed-environment-licensing?WT.mc_id=ppac_inproduct_env%3FWT.mc_id%3DDX-MVP-5003911
Once you review the below preferences on how you want this environment to be managed, you can select the same and click on Enable as seen below –
These will send insights in email. I’ll cover in a separate post and link here.
Once everything looks good, you can Enable.

Editing Managed Environments / Disabling

Here’s how you can edit or disable Managed Environments –

If you are seeing Edit Managed Environments, it means that Managed Environment is enabled for that environment.
And you can disable Management Environment control using PowerShell. You can check this post which highlights how you can do so – https://learn.microsoft.com/en-gb/power-platform/admin/managed-environment-enable#disable-managed-environments-using-powershell?WT.mc_id=DX-MVP-5003911
Snapshot of the document below –

Here’s Microsoft Learn documentation on Managed Environments – https://learn.microsoft.com/en-gb/power-platform/admin/managed-environment-overview?WT.mc_id=DX-MVP-5003911

Hope this helps!

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

Thank you!

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

January 31, 2023 priyeshwagh777 Microsoft Azure, Power Platform, Power Platform Admin Center adls gen 2, data export to data lake, Power Platform Admin Center, power platform data export, power platform data export to data lake, self service analytics power platform

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 –

Navigate to Data Export in Power Platform Admin Center given that you have appropriate rights –
Then, you’ll get to choose amongst the Power Apps or Power Automate data to be exported to Data Lake.
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 –
Now, In the next section you’ll need to choose the Subscription.
Further, select the Resource Group and eventually, the Storage Account as well.

And Storage Account is selected as well.
Once everything looks good, you can click on Create.
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.
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

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.
If you open this folder, since we had chosen Power Automate, it’s folder will be created.
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.
In this case, I had VS Code, so here’s what the Flow data looks like –
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 –

Thank you!

Tenant-Level Analytics in Power Platform Admin Center | For Power Apps and Power Automate

January 30, 2023February 5, 2023 priyeshwagh777 Power Platform Admin Center power platform admin center analytics, tenant level analysis for power platform, tenant level analytics, tenant level analytics power platform admin center, tenant level analytics reporting

As your organization and tenant usage grows, it’s difficult to keep track of Adoption. To tackle this, Tenant-Level Analytics have been introduced in Power Platform Admin Center (https://admin.powerplatform.microsoft.com/).

Let’s see how we can turn this on for your tenant!

Enable Tenant-Level Analytics

Given that you have appropriate permissions in Power Platform Admin Center, here’s how you can enable Tenant-Level Analytics –

In Power Platform Admin Center, look for Settings area – under this, you’ll see an option called as Analytics –
Once you select Analytics, you’ll see on the right-hand side, a simple switch to turn it On. it could be Off by default.
Once you Turn if On and Save, you’ll also see a confirmation message.

And it’ll show this message once applied.
Now, do a complete Broswer refresh.

Reading Tenant-Level Analytics

Here’s how you can review tenant-level analytics once enabled for your Tenant via the Power Platform Admin Center –

When Tenant-Level Analytics are disabled, you’ll not find anything on the top right corner of the Analytics under Power Automate or Power Apps

Tenant-Level Analytics: OFF (for both, Power Automate and Power Apps)

Tenant-Level Analytics: ON
You can drop down on the menu and find Tenant-Level Analytics.
Once you choose Tenant level analysis, you’ll see the below report show up – this is the same for Power Automate as well as Power Apps.
Please note that it takes up to 24 to 48 hours for the metrics to start showing from the previous day.
And after approx. 48 hours later, I see this data now showing up.

Hope this helps!

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

Thank you!

Bulk Delete Cancelling in Dynamics 365 CRM | [Quick Tip]

January 3, 2023 priyeshwagh777 Power Platform Admin Center

In case you want to cleanup some background data in a Sandbox environment but your Bulk Deletion Jobs are failing? Here’s why.

Canceled Bulk Deletion

Below is what you would see –

Once you set a Bulk Deletion job in a Sandbox environment, you notice the below –
The Bulk Deletion Job gets Canceled without even deleting a single record!
There’s a specific reason for why this is happening. Let’s look below.

Background Process

Here’s why the Bulk Deletion job keeps failing –

The reason Bulk Deletion jobs are getting Canceled in the Sandbox environment is because of the Background Processes.
In case the Environment is in Administration Mode.
Open the Environment Power Platform Admin Center (https://admin.powerplatform.microsoft.com/environments) and Go inside the Environment.
Look for the Edit button.
You’ll find that the Administration mode might be enabled. But besides that, the Background operations might be disabled.
This is causing the Bulk Deletion jobs to fail.
And when you restart the process, you’ll find that the Bulk Deletion Jobs will start deleting the items and will be In Progress.

Hope this helps!

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

Thank you!

Run User Diagnostics in Power Platform Admin Center | Solving User Access Issues for Dynamics CRM

December 29, 2022 priyeshwagh777 Power Platform Admin Center Power Platform Admin Center, run diagnostics in power platform, user access issue in crm, user access issue in dynamics 365 crm, user diagnostics

Many users often reports issue of not being able to access Dynamics 365 CRM even when they’ve been assigned security roles.

So, Power Platform Admin Center will provide you a Diagnostic Tool to quickly check what type of access is missing at the administration level across the below areas –

Sign in blocked for the User at M365 level.
No license for Power Apps / CE Apps.
Not in Security Group of the Dataverse/CRM environment

Let’s see how we can run the Diagnostics and how to solve each of them!

Run Diagnostics on Users

Here’s how you can Run the Diagnostics on the Users in Power Platform Admin Center –

Navigate to the Settings once you select the Environment –
Then, expand the Users + permissions area to see the Users option
Once you see all the Users, you’ll be able to see which Users you want to select and then investigate for diagnostics.
When you click on Run Diagnostics, you’ll see the pan on the right hand side complete some tests and then show the results –
And when you zoom, you’ll see the information as below –
So, when you check the License information in the M365 Portal (considering you have Admin access), you’ll identify that the User is missing the license for Power Apps / Customer Engagement Apps.
When I run this for User whose all levels of access are correct, I’ll see the below –
In other instances, the Sign-in could be blocked as well and this is how it’ll appear. The error message will point out what is causing the User to not access the Dataverse environments.
And when you check the User in the M365 Admin Center, you’ll see that the Sign-in is blocked –
And a final reason that a User is not a part of the Security Group which has been assigned to the Environment itself.
In that case, they’ll see the below error –
So, if you check the Environment in PPAC itself, you can see what Security Group has been applied to the Environment.
And if you look at this Group, you’ll not find the member in the Security Group at the M365 Level.

You can find the complete Microsoft Learn documentation on the same here – https://learn.microsoft.com/en-gb/power-platform/admin/troubleshooting-user-needs-read-write-access-organization#user-diagnostics?WT.mc_id=DX-MVP-5003911

Hope this helps!

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

Thank you!

Setting up Billing Policy for Dataverse Environments in Power Platform for Azure Pay-As-You-Go plan | Microsoft Azure

October 31, 2022October 31, 2022 priyeshwagh777 Microsoft Azure, Microsoft PowerApps, Power Platform Admin Center Dataverse, Microsoft Azure, power apps, power platform billing policy, power platform pay as you go

Pay-as-you-go has been recently announced with Azure and I too wanted to explore this topic myself on my trials Dataverse/D365 Sales environment as well as my Microsoft Azure trial subscription which I started.

Disclaimer: Please note that I’m exploring this topic and sharing as I go on. Hence, I’ll continue to write further topics as I proceed. Please try on your Dataverse trial & Microsoft Azure trial subscription to identify / estimate the costs your actual implementation will incur.

I also recommend going through the below Microsoft Learn Pages for detailed information on pricing and meters of the Pay-as-you-go model –

Detailed Microsoft Docs for Pay-as-you-go: https://learn.microsoft.com/en-us/power-platform/admin/pay-as-you-go-overview?WT.mc_id=DX-MVP-5003911

Power Apps Pricing: https ://powerapps.microsoft.com/en-us/pricing/

Pay-as-you-go Meters: https://learn.microsoft.com/en-us/power-platform/admin/pay-as-you-go-meters?tabs=image?WT.mc_id=DX-MVP-5003911

Let’s see how we can get started!

Setting up Billing Policy

Here’s how you create Billing Policy in Power Platform –

In Power Platform Admin Center (https://admin.powerplatform.microsoft.com/), you can see Policies section. If you expand the same, you can see Billing Policies.
Here, you can start by creating a new Billing Policy
You can give it an appropriate name. And it doesn’t allow you to have spaces.
Next, you’ll be asked to select the Subscription you wan to assign the Billing Policy under.
Notice the error below. My Free Trial Azure Subscription doesn’t have a Resource Group created yet. Hence, this need to be present.
Since at this point, I don’t have a Resource Group under the Azure Subscription I selected, I need to go to Azure Portal (https://portal.azure.com/), search for Resource Groups
Since you might not have any Resource Group right away, you can create one.
I’ll just give it a name which I can identify with.
I’ll validate and Create the same in Azure.
Resource Group will be created here.
Now, when I come back to Power Platform, if I reselect the Azure Subscription, I’ll now see that the Resource Group I created is showing up.
I’ll select the same and select United States as the Region.
And click on Next.
In the next steps, I can select which all Environments should be included in the Policy. Then, I can click on + Add to policy.
You can see the Added to policy tab now showing your environment. Once you are satisfied with the selection, you can click on Next.
Final step is to now Review and confirm the policy you are creating.
It’ll take a moment to start provisioning. Then, you’ll see the status as Provisioning.
Once completed, the status will show as Enabled.
Now, when you go back to Azure Portal and open the Resource Group, you’ll find a Deployment show up
Open it up and you’ll see a Deployment created.
And if you open the Deployment, you can see the DataverseBilling which we had set up in Power Platform.
And this point, you are now setup with using Pay-As-you-go plan for your Dataverse environment(s).

Note: Further, I’ll write follow up posts as I explore Pay-as-you-go scenarios and experience myself.