As I stated in my previous post I wanted to demonstrate how to do something in SPD Workflows as well as with Microsoft Flow. In this second part, I am going to be setting SharePoint list-item level security with Microsoft Flow. The steps are very similar, but I still wanted to provide examples for anyone just working away at some of these types of requirements within their own environments.
Something that I have come across a lot is solutions that require setting item level security after a particular occurrence on the list item (or in some workflow process). Specifically what I wanted to look at was how to do it using SharePoint Groups as opposed to AD users, though I will probably cover that later. This is going to be a two-part post as well because I am also going to do it with Microsoft Flow in my next blog. Moving forward, whenever I do a SharePoint Designer Workflow blog I am going to try and do a corresponding one for Flow as well.
This evening I had the extreme pleasure of giving a PowerShell and SharePoint presentation to the Granite State SharePoint User Group in New Hampshire. Presenting remotely was a bit of a challenge as I missed out on the pizza 🙁 and we had a bit of trouble with my demos. Well not really the demos, more the fact that my laptop could not run the VMs and maintain a Skype session. Now, this is not a bad thing about Skype. It actually did really well. The issue is that I tend to go a bit overboard with my VMs. For on-prem demos, I run four fully decked out VMs. I have a DC, SQL Server, SP2016 App and an SP2016 Web server all running on my laptop (yes my laptop is awesome). That uses up all the resources so I couldn’t display my demo at the same time.
That being said I think the session went awesome and I hope everyone enjoyed it. As promised I am providing the slide deck. You can access it here.
A huge thank you to Julie Turner and the other members of the user group. Thanks for joining me.
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
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:
- Preparing SharePoint
- Integrating PowerApps as a Custom List Form
- Customizations All List Form PowerApps Should Have
- Setting a SharePoint People Picker Field Programmatically in PowerApps
- Cascading Drop-down Lists and People Picker in PowerApps
- Create a Flow to be Started Manually
- Creating a Multiple Approver Microsoft Flow
- Sending a Tweet from Microsoft Flow
- Starting a Microsoft Flow from a PowerApp (this one)