Today I want to start a new series around PowerApps and Flow and building out an entire solution that utilizes both of these tools. Until recently, PowerApps was a separate application from SharePoint. It could be attached to a list, but you were still limited to it being outside of the platform. That all changed in the last quarter of 2017 (at least for those on first release). If you are first release and using the new SharePoint list UI, then you can now build your forms in PowerApps like we used to with InfoPath (and some still do 🙁 ) and use them in place of the default SharePoint list forms. This means you can now make your user interface nicer to use and add logic without having to utilize code, an outdated tool or pay for a more expensive tool to do that for you. If you have licensing in O365, you have PowerApps and Flow available to you. In this first post I am going to discuss the requirements and prepare SharePoint. In the next post in the series show you how to integrate and build out your form for the solution. Then we’ll add some logic and customizations to the form. Once that’s done, we’ll bring out Flow and automate the processes behind the scenes. Just a quick note, this series is designed to do as much OOTB as possible so some other logical enhancements like using other control types instead of the default data cards will be demonstrated in future posts.
Posts in this series:
- Preparing SharePoint (this post)
- 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