See Trigger Outputs using Edit Columns in Flow Runs | Power Automate [Quick Tip]

September 6, 2022 priyeshwagh777 Microsoft Flows edit columns in flow, flow runs, Microsoft Flow, Power Automate

If you are noticed a new addition to the Cloud Flows is where you see the Edit Columns in the Flow page.

Edit Columns in Flow

When you open a Flow, you see the below –

These are your usual results of Flow Runs.
And then you open each Flow Run to see what data is passed in the attributes of the steps.
Now, here’s where Edit Columns are a useful new addition if you are using Flows around Sep 2022 time frame.
And then you get to select the attributes from the Flow itself. In this instance, I’m select name and accountid fields from the Flow.
Once your desired columns are selected, you can click Save.
Those columns and their respective values will show up. This will save your effort to go into each Flow to look at what the values are.
And from All Runs page, you can even export these to Excel if you need to.

Hope this was useful!

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

Thank you!

Run As context in CDS (Current Environment) Flow Trigger | Power Automate

October 30, 2020 priyeshwagh777 Microsoft Flows, Power Automate cds, cds connector, common data service, Power Automate

In a CDS (Current Environment), you have to option to Run the Flow under a context of a certain user. And there are a few options from which you can select from – Process Owner, Record Owner & Triggering User

Here’s my Flow in which the trigger is the CDS (Current Environment) connector. Show advanced options and you’ll see that there’s a field call as Run As

Which has the following 3 Options as I mentioned above –

Let’s look at each one of these.

Scenario

To demonstrate Run As, my Flow is triggering on the Update of the Account record, an attribute in the CDS (Current Environment) connector called as RunAsSystemUserId provides the GUID of the System User used in the connector’s Run As field.

You can use triggerOutputs() function to get this GUID from the Trigger Outputs and use it to fetch the System User record. To see how triggerOutputs/triggerBody() works, check this post – Using triggerBody() / triggerOutput() to read CDS trigger metadata attributes in a Flow | Power Automate

Process Owner

As suggested, Flow Owner meaning the one who Owns the Flow

If I select as Process Owner, no matter who triggers the Flow or who is the Owner of the record, the Run As user will be the one who Owns the Flow.

The record could belong to one owner and the other owner might modify it as shown below –

But the Flow will Run As the Owner of the Flow as suggested.

Multiple Owners?
In my test, I believe the one who created the Flow becomes the first Owner and hence, is what it appears in Run As

Record Owner

Easily, the record Owner in Dynamics 365 is the Owner of the record, so no matter who triggered the Flow or who the Flow owner is, the Record Owner will be the Run As user.
In this example, Priyesh Wagh is modifying the record Owner by Kuldeep Gupta, the Flow Run As will show as Kuldeep Gupta

Triggering User [Also Default]

If the Run As is set to Triggering User, whoever caused the Flow to Run is the Run As context user.

Let’s say Kuldeep Gupta is a user is modifying a record Owned by SYSTEM, the Run As user is Kuldeep Gupta.
Now, if there’s no Run As selected or even if there are multiple Owners to the same Flow, the one who causes the Flow to run, is the context user of the Flow.

Let’s say Priyesh Wagh modified this record owned by SYSTEM, the Flow will Run As Priyesh Wagh

Hope this helps!!

Here are some more Power Automate related posts you might want to look at –

Thank you!!

Number Formatting in a Flow | Power Automate

May 13, 2020September 26, 2020 priyeshwagh777 Microsoft Flows, Power Automate flow, Microsoft Flow, number format, Power Automate

Quite obviously this is one of the most common asks in Flow to format a number. Here are some ways to do so using Format number Action in Flow (Power Automate).

This is available in Format number action in a Flow in Power Automate. This is available in Number Functions connector.

Commas and Decimals

For a standard simple number, you can simply denote by # and commas or other symbols where needed. Here, I won’t select any locale.
And it would render into this –

Phone Number

US phone is an example where it is denoted by brackets and dashes in between. I’ll select English (United States) (en-US) in the locale among others. So, my format would be.
And the resultant phone number will be set as below

Currency Input

For currency, this is what I did –

Added ₹ followed by ##,###,###. I’ll select English (India) (en-IN) in the Locale field.
So even though my number value i.e. (50000) is in thousands and not hundred-thousands as I covered in my format, it’ll consider the correct format used and my output will be –

Here’s where you can look at other ways to format numbers –
1. Standard numeric format strings
2. Custom numeric format strings

If you’re looking for some more posts on Flow / Power Automate, I’ve written some in the past. Check these –

Hope this helps!

Switch-Case in a Flow | Power Automate

April 29, 2020 priyeshwagh777 Microsoft Flows, Power Automate Microsoft Flow, Power Automate, switch case

Some of the common operations / decision making one wants to perform in terms of programming is definitely switch-case!

Here’s how you can do it in power automate

Scenario

To keep things simple, I will simply reflect the name of the OptionSet value in a variable in Flow –

1. Here’s my OptionSet called Account Type with values Customer [1], Vendor [2] & Partner [3]

1. My Flow will be called on update of Account record’s Account Type field change

1. I’m simply using a variable to store the value of the selection made on the field.

Using Switch

Now, let’s get to the important part –

1. If you search for Switch under Control, you’ll see as below

1. This will first ask you what the Switch should be on, in this case, it’s the Account Type value to be selected from the dynamics values

1. Now, I can start entering the Cases one by one as shown below and setting the variable I created above. For value in Equals 1, I’ll set variable as Customer
  
  Clicking on the + [Plus] sign in between Case and Default will let you add more cases.

1. Finally, once all the cases are entered, the Flow will start looking something like this from a hawk-eye-view with the Default case appearing in the end.

Working

Let’s look at how Switch-Case would work –

1. I updated the Account Type field with Vendor

1. Switch on the Account Type Value (selected from Dynamic Values) will reflect the value of 2

1. And Case 2 will execute simply reflecting what is stored in the variable. Rest of the cases will not run

Pretty Easy! Hope this helps!

Setting Retry Policy for an HTTP request in a Flow | Power Automate

April 19, 2020April 19, 2020 priyeshwagh777 CRM with .NET Web Applications, Microsoft Flows, Power Automate http request in flow, Microsoft Flow, microsoft power automate, retry policy

Often times, There could be an issue where your HTTP request isn’t hitting well. So, to overcome this, you might want your Flow to Retry after a certain duration and for some number of times.

You want to setup a Retry policy for the same. Here’s how you do it!

Setting Retry Policy

Follow this to setup a Retry Policy of your Flow

Locate your HTTP step and navigate to Settings

Once you’re in Settings pane, scroll below and look for Retry Policy.

Default type is set by default, if you expand it, you can select what should be the Retry Type. In this example, I’ve set to Fixed Interval for simplicity
Default is set to 4 retries at an exponential interval. (Exponential increment type is a little confusing to explain, you can check this post as users discuss how exponential time increments work – )

In Fixed Interval type, I’ve set number of retry count to be 3 and duration between each retry should be 30 seconds (represented in ISO-8601 format)

With that, the policy is set. And the HTTP request step will try for 3 times at the interval of 30 seconds each.

If you want to test using some HTTP request, you can sample HTTP requests from here – https://httpstat.us/

How it works

Look for Failed Runs to see the result –

Open a Failed Run where you know HTTP request could have failed

Now, look for your HTTP request where you set the policy on. Expand the same.

Upon expanding, you can see that there were 3 retries and it failed due to a timeout i.e. 408

You can also check on the right hand side of the page which says that the total duration of all these retries were 1 min 30 seconds

If you observe the Flow Runs, you can find the the Flow did consistently try to run at an interval for the number of times specified.

In case you’re looking for more Flow/Power Automate related posts, check below –

Hope this helps!!

Using Parse JSON to read individual List Records in Flow|Power Automate

April 12, 2020April 12, 2020 priyeshwagh777 CRM with .NET Web Applications, Microsoft Flows common data service, Microsoft Flow, Microsoft Flows, Power Automate

This is a scenario I came across when I was using Common Data Service connector [not Common Data Service (Current Environment)] connector to read Opportunities tied to an Account.

Example

In this scenario, I wanted to retrieve the Opportunities tied to an Account. So, my filter query was _parentaccountid_value(‘ACCOUNT_IDENTIFIER’)

Here’s my Flow starts. I want to read Opportunities that are tied to my Account in context –

Flow Inside a solution vs. Outside a Solution

Inside a Solution

Now, when I had this Flow inside a solution, the result didn’t have a body and instead just gave me Status Reason value as below –

Outside a Solution

Whereas, outside the Solution, I was able to get the array of Objects i.e. Opportunity data in the Body in the Output itself.

So, what can we do about the Flow which is used inside a Solution and you want to actually see what was the output? You may or may not require to see the records (depending on your implementation)

But let’s say you want to see what was returned, let’s just parse these results as is using Parse JSON to see what we got.

Use Parse JSON from Data Operation

Another way to read what you’re retrieving is using Parse JSON Data Operation.

Search Parse JSON and you’ll see the result in Data Operation type of Actions as shown below –
Now, you have to apply this to Current item from the retrieved List records in Apply to each operation. In case you don’t have the schema or not sure what to put it in. Simply use {} in Schema field. This will just pass through as is.

Checking Result

Now, let’s test using the above and see if we can get the results

Now, you can actually see the Inputs and Output of Parse JSON which is basically the same. This is useful if you want to visually see what’s going on through your Flow.

But, if you don’t want to see what’s being passed through when in Production? You can Secure Input/Output in Power Automate Run History

Hope this helps you!!

Create a To-Do List Item of Important Outlook Emails using Power Automate

March 9, 2020 priyeshwagh777 CRM with .NET Web Applications, Microsoft Flows, Power Automate Microsoft Flows, Microsoft To Do, Outlook Email, Power Automate

Since Power Automate is so powerful that you can creatively use it to improve your productivity at work. Here’s an example of how you can utilize a scenario where you need a quick checklist to make sure you respond all important emails for the day.

Power Automate

You’ll need to create an Automated Power Automate and select the trigger as Office 365 Outlook. Select ‘When a new email arrived (V3)’ from the same and make sure you only select the High Importance marked emails
Next step, create a To-Do Item. Select the List you have created. In my case, I created a separate list called ‘Respond Important Emails’

And the step to configure the To-Do List item should be like this –

In the above picture, I’ve made sure I select the correct List I want to create a To-Do in.

And to give myself some time, I’ve added a reminder time of 2 hours from the time this Flow/Power Automate will run i.e. when the email will come in –

How it works

Now, when an Important email will arrive in my Inbox as below –

Power Automate will create a To-Do in my created List

And it will look like this –

Also, the reminder is set to remind me 2 hours post the time the To-Do item was created. Just in case I’m into something else, I’d set myself a reminder.

Hope this helps! And you can use your creativity to improve your productivity!

Selecting (Current) in Environment in Power Automate CDS connector and why it matters

February 25, 2020September 26, 2020 priyeshwagh777 CRM with .NET Web Applications, Microsoft Flows, Power Automate Microsoft Flow, Power Automate, Power Platform

If you’re new to Power Automate, you must be wondering why am I given an option to select either (Current) or the actual name of the environment. Why can’t I just select the actual name?

Well, here’s why –

Importing into Other environments

So, when you import your Flow / Power Automate into other environment using a solution, be it from Sandbox to Production or to entirely different org in different tenant, here’s the behavior

(Current) selection

And if you Export this Flow and import into other Organizations, you can simply restore the connections to that organization by simply selecting the connection

And it will be loaded with the current environment(s) as it was on the source environment

Environment selection

Whereas now, if you have exported the Flow with Environments selected as the particular environment and not (Current) like below –

When you import this into other environment, and when you try to authenticate, it will not go through and you’ll see something like this –

And if you wonder what the Org name is displayed in the picture above, it’s the Org Unique Name of the source environment

And that’s why, it’s critical to select (Current) environment when you develop flows and you know you want to have these imported to other environments.
Here’s Microsoft’s Current Environment connector’s official Docs – https://docs.microsoft.com/en-us/connectors/commondataserviceforapps?WT.mc_id=DX-MVP-5003911

Hope this helps!

Create your own Insight Cards with Power Automate in Sales Insights

November 19, 2019 priyeshwagh777 d365 for sales, Microsoft Flows, Microsoft PowerApps, Power Automate Dynamics 365, dynamics 365 ai for sales, dynamics 365 for sales, Microsoft Flows, Power Automate, sales insights

Sales Insight’s cards are not just restricted by what is provided by Sales Insights for your Org, you can make your own using Power Automate too. Here’s how –

Requirements

These features aren’t free under Free Features of Sales Insights. Sales Insights license is for $50/user/month. More info on licensing here – Sales Insights Licensing

For free features, only pre-defined Insight Cards show up. You don’t get to create your Cards. To try this feature, you can create a 30-day Sales Insight trial.

Scenario

Let’s say you have a custom field on the Account called as Renewal Date which holds a Date of renewal for an account. And you want to create an Insights card to show up whenever this date is within 5 days –

Create a new Insights Card using Power Automate

Let’s say you have Sales Insights already setup in your Org and you have moderate knowledge of Power Automate (formerly known as Flows)

Navigate to Sales Insights settings in Sales Hub > Global Settings > under Assistant Studio, look for Home and you’ll see a button to Create a new Insight card.
Since our requirement is a pretty common one and Power Automate has a template for it already, you can select one or even start from scratch.
Make sure all the permissions are correct and you’re set to modify a Power Automate Template (or create from scratch)
Let’s say you are making this run on a daily business during your non-business hours.

Little Tweak to store a Reminder Date in D365

I wanted to have a custom reference of the Reminder Date in my own way in D365 instead of making the Power Automate query more complex.
I’ve created a Calculated Date field for RenewalReminder to store date of 5 days before the Renewal Date and this will be maintained for all records.

So that the field stores 5 days prior to the Renewal Date

(I’ve hidden it away in actual implementation later on)

In the past, I’ve implemented a similar scenario to store current date used for views in D365, reference Blog: Store ‘Today’s Date’ in a field to use in workflow conditions in D365 CE

Design Power Automate

Since we’ve chosen a template to get a reference from, feel free to remove/modify whatever you need to –

Now, I want to Flow to be triggered every day at UTC midnight

Details: Every midnight, fetch me Accounts where I RenewalDate has passed so that selective Accounts will be queried, and then I want to create cards for those accounts in the next step.
And I’m only comparing the RenewalReminder field value to the current date since it will run everyday
In the final step, for Each account, I’ll create a Card with the Account’s details which the user needs to see.

I’ve set some properties which are quite self-explanatory. I’ve made the Open button on the card to open the record itself.
And I’ve also made the card to show up only until the Renewal Date. (Maybe setup a separate process for Accounts past renewal date)

And that’s that! Your Power Automate is ready to create Insight Cards which remind you of an upcoming renewal

Seeing it Run

Now, every day when the Power Automate runs, it will create Insight cards for you and they’ll appear as you’ve configured them. In this case, For Alpine Ski House account, the Renewal Date is 20th Nov, so the card has started showing up since 5 days before the Renewal Date (Date stored in RenewalReminder for referencing, you can choose your own way to do so in Flows)

Even in your Dashboards, since you’re the owner of the record and it’s set to show only to the owner, you’ll see it and clicking on the Open button will open the Account record itself

Hope this helps!!

Sending Image from Canvas PowerApps to SharePoint Document Library using Flows

June 12, 2019 priyeshwagh777 CRM with .NET Web Applications, Microsoft Flows, Microsoft PowerApps business process flow, flows, Microsoft Flows, msflows, Power Platform, powerapps

One of the most common requirements is to upload images to SharePoint using PowerApps. From my learning from various sources, I’ll try to “demystify” my explanation to send/upload an image to SharePoint Document Library using Flows on my Canvas PowerApp.

Ingredients

Assuming you have the following things already in place in PowerApps as well as in SharePoint

PowerApps’ Camera/Image control and a Submit button. In my case, the image above is a camera so that I capture the image I want and the image below is the Image control to show me what I clicked.
A SharePoint Document Library to record, say, Incidents.
We will get to the Submit button on the PowerApp once we create our Flow.

Flow

Let’s create a Flow to pick the Image from your PowerApp, convert it to binary and send it to the SharePoint Document Folder location called Incidents.

Since we want to trigger the Flow from the PowerApps itself, we will select the trigger of the Flow as ‘From PowerApps’ and hit Create
Once your Flow is ready, leave the first step of PowerApps because that’s the trigger. Add Step to create a SharePoint file and fill in the details of the Document Library you have created.
Fill in the FileContent as above. You’ll need this to be converted in the intermediate step after this.
Now, you’ll need to add an additional step in between PowerApps and the Create SP File step as below. It will be a Compose action.
In Compose action, under Expression, select dataUriToBinary expression and make sure you open the bracket as well.
Now, go back to the Dynamic Content section and select the CreateFile_FileContent to complete the formula.
Click OK on the screenshot above and the formula should be set.
Now, replace the File Content section to take in the Output of the Compose step.
Save your Flow and your complete Flow should look like this.
I’m naming my Flow as ‘IncidentFlow’ so that I can identify it.

Adding the Flow to Submit button

Going back to the PowerApp, let’s Run this Flow on the selection of the Submit button and pass the image.

Now, select the Submit button, and on the Formula bar, add the Flow you created, I named it IncidentRun. Select the same so that the Formula comes as IncidentRun.Run( for you to pass on the image.
Now, pass the latest image on the collection i.e. the same image which is being displayed in the image control below.

Running the App

I just ran the app on the desktop itself, you could do it from your phone too!
So I clicked on the Camera when I was ready, the image appeared in the image control and I that was what I wanted to upload. So I clicked on Submit button.

The flow was successful

And my image was in SharePoint too!

I know it is a lengthy post but I tried to summarize as much as possible. Make sure you have a way to uniquely name each file or else, the same file will be overridden.

Thank you!

Edit Columns in Flow

Share this:

Like this:

Scenario

Process Owner

Record Owner

Triggering User [Also Default]

Share this:

Like this:

Commas and Decimals

Phone Number

Currency Input

Share this:

Like this:

Scenario

Using Switch

Working

Share this:

Like this:

Setting Retry Policy

How it works

Share this:

Like this:

Example

Flow Inside a solution vs. Outside a Solution

Inside a Solution

Outside a Solution

Use Parse JSON from Data Operation

Checking Result

Share this:

Like this:

Power Automate

How it works

Share this:

Like this:

Importing into Other environments

(Current) selection

Environment selection

Share this:

Like this:

Requirements

Scenario

Create a new Insights Card using Power Automate

Little Tweak to store a Reminder Date in D365

Design Power Automate

Seeing it Run

Share this:

Like this:

Ingredients

Flow

Adding the Flow to Submit button

Running the App

Share this:

Like this: