Nishant Rana

Fixed – Flow client error returned with status code “Forbidden” and details – MissingAdequateQuotaPolicy, the user does not have a service plan adequate for the non-Standard connection in Power Automate

Recently one of the users reported this error while trying to Test a flow.

Request to XRM API failed with error: ‘Message: Flow client error returned with status code “Forbidden” and details “{“error”:{“code”:”MissingAdequateQuotaPolicy”,”message”:”The user ‘8a47d139-662e-4b73-bca3-53a59e8bebeb’ does not have a service plan adequate for the non-Standard connection ‘Microsoft Dataverse’. https://go.microsoft.com/fwlink/?linkid=2123710″,”extendedData”:{}}}”. Code: 0x80060467 InnerError: ‘.

As here the Premium Dataverse connection was being used, the resolution was to either purchase a Per User plan or Per Flow plan or to enable the trial of Power-Automate per user plan.

After the trial was enabled for the user, the error got resolved.

Hope it helps..

Advertisements

[Step by Step] Dataverse | Connect Cloud flow with Service Principal (Application User)

Rajeev Pentyala – Technical Blog on Power Platform, Azure and AI

By default, Cloud flow Dataverse connectors run under the Owner (i.e., User who created the flow) context. When the flows move to different environment via solutions, connectors run under the user account who imported the Solution.

Making the flows run under interactive user accounts is not recommended as they cause confusion when we check the record’s audit for who updated the record. Its recommended to make the flow run under ‘Application User’, if the calling user can be a fixed account.

In this article lets see how to make the flow run under Application User using Connect the flow using Service Principal option.

High level design:

Following are the steps we gonna go through.

App registration in Azure Active Directory (AAD)
Create an Application User in Environment.
Create a Cloud Flow and connect with Application User.

App registration in Azure Active Directory (AAD)

Connect to Azure Active Directory Admin Center

View original post 242 more words

{Power 2022} Enable editable grid on a Dashboard component in Dynamics 365 CE

MSDYNAMICSBLOG BY DEEPESH

Requirement: Enable editable grid on a Dashboard component for views.

Solution:

Follow the following steps to configure editable grid on a view component within Dynamics 365 CE dashboard:

Open the Dashboard for editing by clicking Edit:

Double click the View component in which you wish to add Editable Grid control and select control tab:

Select Editable grid in the control and set relevant option (selected Web in our example in the blog):

Clock Ok and then Save, Close the dashboard(using Personal Dashboard in this example)

Result:

Hope it helps!

Power 365ing as usual!

Any problem in Power Platform or Dynamics 365 – end user, Microsoft partner or an individual?

Problem Area – Technical, Functional, Training, Development or consulting?

Me and my team are here to assist, please fill the following form for your business needs:Click here

View original post

Understanding Change limits option in Do until control – Power Automate

Within Do Until control in Power Automate we have the option of defining the limits i.e. how long the do until will run either based on count or timeout.

By default, the value for count is 60 and Timeout is PT1H which equates to 1 hour i.e. it will either run 60 times or will run for 1 hour which occurs first.

Let us set the count to 5 and test it.

We have also added the delay of 1 minute along with the condition for do until and triggering it on the update of a lead record.

As expected if the condition is not true, after running 5 times it stops successfully.

Now let us change the Timeout to 2 minute and we keep the count as 5.

As expected after 2 minutes (by that time it has looped 2 times with 1 min delay), the flow stops successfully.

The flow will also be successful when the Do until condition is met.

Here we can make use of Current Iteration Index property of Do until to find out the number of times it has looped.

To set the time out format –

https://www.digi.com/resources/documentation/digidocs/90001437-13/reference/r_iso_8601_duration_format.htm

Lastly the Count value can be maximum 5000 –

Also check –

https://nishantrana.me/2022/05/17/fixed-invalid-template-unable-to-process-template-language-expressions-in-action-template-language-expression-cannot-be-evaluated-the-template-action-is-not-defined-in-the-current-scope/

https://nishantrana.me/2022/01/19/how-to-use-do-until-and-delay-in-power-automate/

https://nishantrana.me/2022/05/19/filter-rows-and-trigger-conditions-in-power-automate/

Hope it helps..

Advertisements

Terminate and Cancel Flow Run in Power Automate

Cancel Flow Run action which is part of the Power Automate Management connection be used to cancel a running flow along with Terminate.

Cancel Flow Run

We can specify the below expressions for its parameters as below.

Environment	workflow().tags.environmentName
Flow	workflow().name
Run ID	workflow().run.name

The Cancel Flow Run can be used inside Do Until and Apply To Each control, unlike the Terminate.

If we try using Terminate inside Do Until we will get a similar error message as below.

Request to XRM API failed with error: ‘Message: Flow client error returned with status code “BadRequest” and details “{“error”:{“code”:”InvalidOpenApiFlow”,”message”:”Flow save failed with code ‘InvalidWorkflowRunAction’ and message ‘The workflow run action ‘Terminate’ has type ‘Terminate’ that is not allwed to be nested under an action of type ‘until’.’.”}}”. Code: 0x80060467 InnerError: ‘.

If we have implemented the Try, Catch and Finally block (scope), the Catch and Finally steps will be skipped as shown, on canceling the flow.

Interestingly the steps next to Cancel Flow Run still run.

The status will show up as canceled for the flow in the flow history.

Now let us see what happens in the case of Terminate action.

In the case of setting the Terminate Status as Failed – we see the next step skipped along with Catch and Finally.

Let us see in the case of Status = Cancelled

The status will be Canceled.

In the case of Status = Succeeded,

Here the status will be Succeeded.

Do check –

https://sharepains.com/2018/09/11/microsoft-flow-never-terminate-your-flows-unless-you-like-failure/

Hope it helps..

Advertisements

Fixed – Azure Synapse Link for Dataverse not starting

Recently while trying to configure “Azure Synapse Link for
Dataverse” for one of our environments, we faced an issue, where it got stuck as shown below.

Also, there were no files/folders created inside the Storage Account.

Posts on Azure Data Lake

The accounts were properly setup – https://docs.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-synapse#prerequisites

Here we had only selected contact table for sync initially, and it had around 2.5 million records.

To fix this, we unlinked (using Unlink Option) and created the link again and this time we selected a table having very few record for e.g. country table as shown below.

This time the sync started immediately.