On 21st August 2019 Microsoft announced that actions in Microsoft Flow from Outlook stack, are going to be moved from using Outlook REST API v1.0 to Microsoft Graph v1.0. Along with that information there was also written, that current Outlook API 1.0 is going to be decommissioned in 1st of November 2019. So after that date all old actions in Microsoft Flow are going to be removed too.
This post extends what I wrote in a previous one about Try-Catch pattern in Microsoft Flow. In this writing I am focusing on how you can log errors that occurs in your Microsoft Flows in a single place, using Azure Application Insights.
Recently I had a pleasure to show my presentation during Microsoft Flow Online Conference 2019 about building errorless workflows in Microsoft Flow. Actually, it was more about logging and debugging to receive errorless workflows in the end.
The post you are reading now was inspired by a recent question I saw on my Twitter. User was asking if it is possible to reassign a task to another employee if the current assignee is out of office without an access to their Office 365. I found this question as a direct link to a well known functionality of business applications called “substitutions”.
The only trigger built-in in Microsoft Flow for Twitter is “When a new tweet is posted”. However, the list of events available in Twitter API account activity documentation is much wider, built of 19 options. But how to get to them?
This post is related to a screencast I’ve made recently. It describes how the Flow, used by the solution, is built in details. Have fun watching and learning how it is made. This post is also part of the sequel I am writing about “Adaptive Cards“.
It was fairly easy to say to SharePoint Workflow (both in 2010 and 2013 versions) that certain action or actions should be executed with the elevated permissions.
When preparing for a new project, I started to check whether different customer expectations are feasible with PowerApps. The first of these is the ability to use an XML file as input, to build a table in the application and possibly to save them to SQL later.
In my daily work over business processes in Office 365, specifically in SharePoint Online, one thing annoys me the most – namely the lack of mechanisms to inform me that the workflow has hung up – that it is in a “Suspended” state.
The solution for that issue is not provided by Microsoft or Nintex – the company with which products I have been working for a quite long time. There are only workarounds, but they are inadequate, and I wanted to be able to react proactively and not reactively to any flow suspension event.
Customer asked me if this is possible to add handwritten signature to a PDF generated using tools available in Office 365. My first thought was “no”, then I checked that there is “Pen input” control in PowerApps, so it was like “yes”. Then again, after searching “how” this signature can be put inside a document, I thought this is a “no”.