Flow: Create Planner Task and Include Attachments From Outlook Email

Hi everyone. One of the many great things about being a Flow Community Contributor and having a love for building Flows, is that there are countless opportunities to create Flows for others. In this blog post, I will take you through a real word example where our community member js4 had asked for guidance on how to create planner tasks from email. This request came in three tranches, presumably as the potential for Microsoft Planner working with Flow, as an engine, became clearer and clearer as we stepped through the processes. You can find js4's post here.

It then became apparent to me after searching our forum, others were requesting extra functionality from Planner and Flow also. Please see the following link.

Planner attach document from Outlook email

With 94 up votes and posts as recent as January 24th 2019, I thought I'd give this a go as I could see it's feasibility, despite no template or process for it as of yet.

So here is some information on the Flow before I step you through each action and how to create this for yourself. Oh, and don't forget, this Flow will still be created and updated with a suitable description from the body of the email if there are no attachments.

Note: Where I have used expressions, or even if there may be potential questions asked around what action provided the value for the dynamic content, I will feature these directly below each image in order. There will be times when the comments section of the action holds this data too.

Prerequisites: The use of a SharePoint Document Library is required. From Documents(Shared Documents), I have added a folder called "PlannerDocs". You may want to create this for consistency and to make it easier to follow along.

Read More

Flow: The Sweetest Graph Call You've Ever Seen – Hiding Data in Flow

Hi everyone. Calling APIs from Microsoft Flow is a key part of what I use it for, as it allows me to harness data from the cloud and do useful things with it. More often than not, it helps with the creation of automated processes linked to Office 365, SharePoint and Azure, that I do so much with. Whilst doing my thing in the Flow Community Forum, I stumbled across a post from community member Roger365.

He names his post "HTTP OAuth with Client Secret" and goes on to say.

"Why do i see the client-secret as plaintext in the "Secret" field? If i would share my FLOW the other users, they will also get the client-secret. Why is that field not of type "password"? (So the value will not shown as plain-text.). At now, the secret can be reused and for me its a security issue."

Here is the post

He makes a valid point, although these fields are not password fields as they are able to take dynamic data and expressions so it is likely for that reason they are the way they are. There is no obvious way to hide data in Flow, but when I read a post from everyone's favourite #FlowNinja he put me well and truly on the scent for hiding data. Kudos to John Liu for all his wonderful insight relating to Flow generally.

So here is how I now approach hiding values and in this example I will use it to make "The Sweetest Graph Call You've Ever Seen", for now anyway.

Read More

Flow: Try, Catch on User List Till You Get A Match.

Hi everyone, so "Template Tuesday" has come and gone and what a lovely little offering the Flow Team have packaged up for you. The scope action is one I don't see in use too often, but when you consider it's power it really is one for the watching, and the using! The fundamentals behind Try, Catch, Finally is how it has been dressed up and it works a treat. Have a look at the tweet below and see more details of the template there too.

Read More

Flow: Testing Various Date Formats From Any Source

As a Flow community contributor, I regularly assist Flow users with the creation of their Flows. The great thing about a community like the one you can find at this link is that when I need assistance with an expression, an Odata filter or the use of a connector, help is never too far way. You just can't beat support like that when working with technology.

One of the common queries that comes up relates to the use of dates in a Flow. Dates and times are an essential part of application building, business processes and day to day life so we may have to say something like the following.

If due date is next 7 days do X, If not do Y.

If current date is 2 days before user 1's birthday (taken from a SharePoint List perhaps) send me a reminder so I can get them a present.

Get all tasks for the next 14 days from a SharePoint List and send a Monday email with these tasks.

The above examples, are merely just a snippet of some of what comes up relating to the format of the date or the expression required to match a date requirement.

But what methods are suitable to test these scenarios if it's just not working is not working for you?

Read More

Flow: So Where has "Edit in advanced mode" Gone on Condition Actions

Below is an image of the new format for conditions in Flow. Look at the no code control we have here with real conditional logic. What in improvement and one I am sure the community and users will embrace overall. Well done to the Flow Team, one of several great improvements I am seeing on my Twitter time line just now.

Full detail at this link:Β Build more powerful conditions in flows and more

Image credit:Β https://flow.microsoft.com/en-us/blog/build-more-powerful-conditions-in-flows-and-more/

Read More