Migrate Flow to latest Microsoft Dataverse connector

March 31, 2023 priyeshwagh777 Power Automate dataverse connector, migrate flow, migrate to the new dataverse connector, power automate dataverse connector

If you are using the legacy Dataverse connector which has the gray logo and looks like the below.

You can run Flow checker to identify if Power Automate can help you migrate the Flow to utilize the latest connector.

Flow checker message

Here’s what the old Flow looks like –

You would see the below message once Flow Checker suggests you changes –
Once you click on the “Open the migration assistant” link on the suggestion, it’ll pop-up a window to ask if you are ready to allow Migrating the Flow to the latest Dataverse connector.
Once you click on Migrate, it’ll start the migration process and based on how lengthy your flow is – in a few moments your new Flow will be ready.
So, once the migration is completed, you’ll see a message like this.
Once you click on Open the new flow, you’ll notice that the new Flow now has (Migrated) written in.
And once you click on Edit, you’ll see that the Flow step where old Dataverse connector was used has been replaced by the new Connector

Hope this helps!

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

Resolve Project Operation errors | PSS Error Logs

March 27, 2023 priyeshwagh777 Project Operations Project Operations, pss error logs

In case you are new to Project Operations or have recently upgraded from Project Service Automation to Project Operations, and if you are running into some issues, here’s how to identify them

Error

Here’s an example error –

Let’s say you are trying to add Tasks to the Schedule in Project Operations, and you see the below error in a few moments.
Now, if you look at the above error in red, it won’t let you know exactly is the issue. Hence, here’s how you find it. Check the next section.

PSS Error Log

Here’ s how you can get to where the error is –

You can look for the issue in the below section –
Go to Settings in the Project Operations App.
Then, go to the PSS error logs and you’ll find an entry there.
And once you open it up, you’ll find the issue there. There could be different issues based on what operations you are trying to perform in Project Operations.

Now, based on your knowledge of Error Resolution in Dynamics 365 CRM application, you can work towards solving your errors.

Hope this helps!

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

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.