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)