This spring I had the great privilege of speaking in front of a great room of people at SharePoint Saturday Montreal. At this conference i outlined how easy it was to build a great solution from conception to implementation using just PowerApps, Flow and a few connectors. In the space of half a session (I had to do some talking too ;-p ) I build a full solution using PowerApps, Flow, SharePoint and Azure Database. As promised here is the slide deck from my presentation.
Today I was trying to build a flow that kicked off from the Flow Launch Panel in my library. To do this for a list you simply need to create a flow based on the trigger “for selected item”. Once published the Flow Launch Panel is enabled on the list and you can now launch any flows that are attached to the list manually. You can do this for a library as well. The difference however is for a library you want to use “for selected file”. Seems really straight forward and easy right? Sure if it worked as expected.
Problem: Microsoft Flow Trigger “For Selected File” Missing
So here’s the problem. When you create a new flow a lot of people select the platform they are working with to decrease the count of the items to choose from. This one little step is what causes the problem. Allow me to illustrate. I created a new flow and wanted my trigger to be when a SharePoint file is selected in a library. So I created the flow, selected SharePoint and started to type “select” to filter the list. Here’s what I got:
Resolution: Easy, But a Workaround
The fix\workaround is so simple I hope Microsoft can fix it soon. To select the missing trigger, DON’T select SharePoint as the platform. When you start to type in your filter, it will actually show up before the “for selected item” trigger.
Thanks for reading!
I had the great pleasure today of speaking at the Global Integration Boot Camp. The boot camp is a worldwide event and I was speaking in Calgary, Alberta Canada. There was some great content and I was able to share how easy it is to create integrated solutions with Microsoft Flow and PowerApps. There was a great room of people and some fantastic questions and discussion. As promised here is my slide deck from today.
Had the great pleasure of presenting to the O365 User Group while I was at MVP Summit in Redmond Washington this week. The presentation shows how it is possible for organizations to protect their data flow within O365 and Power Platform. Thanks to everyone who attended and here’s the slide deck:
We come to the fourth and final post in my series on deploying a SharePoint 2019 Development Environment. In this post, we will install SharePoint 2019 with AutoSPInstaller. AutoSPInstaller is a great tool that allows you to set all the configuration of your environment from an easy to use GUI. It then exports your settings as a config file for a batch process that will install and configure your entire SharePoint environment from installing the binaries to configuring your site collections. It’s a far cry from sitting at an install screen waiting for everything to finish and then having to configure it again for the next server. Setting up the config file may take some time, but it will benefit in the end because it will install all of your servers for you.
If you are interested in checking out the other items in this series click on the links below:
- Install and Configure SQL Server 2017 for SharePoint 2019
- Preparing Servers for SharePoint 2019
- Install SharePoint 2019 with AutoSPInstaller (This one)