All posts by DaveD

Email an External User in a SharePoint 2013 Workflow

I am sure we can all agree that at some point or another we had a need to email a user that did not have an account within our domain via a SharePoint Designer (SPD) 2013 workflow.  And while attempting to set it up we were surprised to find out it wouldn’t work.  Not only did it NOT send the email, but to add insult to injury the attempt actually would suspend the workflow if forced to try.  If you have never had the need, well thanks for coming to my post anyways and let me tell you… it can’t be done.  An easy workaround is to build a SharePoint 2010 workflow, which doesn’t have this limitation, but then you lose the other fantastic benefits of a 2013 workflow.  Microsoft removed this ability as a security enhancement.  Today I am going to demonstrate how to email an external user in a SharePoint 2013 Workflow.

Quick note: Microsoft Flow does NOT have this limitation.  I am describing how to to it in SharePoint Designer because so many still use this tool

Read more

Building a Modern SharePoint Solution: Part 9 – Starting a Microsoft Flow from a PowerApp

This is the final post in my series of building a modern SharePoint Solution.  In this post, I will demonstrate starting a Microsoft Flow from a PowerApp.  There are many reason’s why you would want this, but the most often used would likely be to allow the user to update an entry, save it and hold off sending it until they have all the information in place.  There are alternatives of course; like having a Flow wait for a value to change, but I prefer the user experience a button submission gives you.  Special note: Because Flow doesn’t currently allow for multiple triggers for a flow, we won’t be able to use flow created in Part 9 of this series.  However, I do suggest you not remove not remove it because this allows multiple ways to kick off the WF.

Posts in this series:

Read more

Building a Modern SharePoint Solution: Part 8 – Sending a Tweet from Microsoft Flow

In my previous post, I showed you how to set up multiple approvals in a workflow. This post is going to continue along the requirements I set out in part 1 of this series.  I’ll be walking through sending a tweet from a Microsoft Flow.  It’s pretty straightforward.  Microsoft even has it as a template I believe, but I still wanted to illustrate how to do it because this is actually part of a bigger flow and an item in a solution’s requirements.  We’ll be continuing on from where I left off in part 8 of this series, but the steps I have here can be picked up and added to any flow you will be working on.

Posts in this series:

Read more

Building a Modern SharePoint Solution: Part 7 – Creating a Multiple Approver Microsoft Flow

In my previous post I showed how to set up a flow to execute manually and not on an add or change event.  I have a reason for that we will get to in a future post, but for today I am going to cover creating a multiple approver Microsoft Flow.  In our requirements we have both a project\event approver as well as a manager approver.  One thing you don’t see on the form, but was mentioned in the requirements is the need for communications to also approve.  This will be going to a generic account (for now) that anyone in the communications team can deal with.  The process is the flow will request approval from the project approver first, then the manager and finally communications cause they are not checking for content just grammar and such.  No sense including them until the other approvers are ok with the message.

Posts in this series:

Read more

Proper way to handle workflows that throw a Microsoft.Workflow.Client.ActivityValidationException

I had to build a fairly complex workflow not long ago.  The workflow was built in SharePoint Designer 2013 and had a lot of moving parts to it.  So many, that when I went to publish it I received the following error message: “Microsoft.Workflow.Client.ActivityValidationException: Workflow XAML failed validation due to the following errors: Activity “SomeXActivity” has 65 arguments, which exceeds the maximum number of arguments per activity (50).”  This error message is actually telling us that our workflow has too many variables within it.  Basically, this is happening because when the workflow is running the Workflow Manager has to manage more 58 (in my case) variables.  Workflow Manager only allows there to be 50 variables in the workflow… by default.

Read more