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, a PowerApp 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 the 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.
I have always been a strong supporter of the SharePoint Business Connectivity feature. I find that in many cases it allows for easy access to data you would normally have to develop custom solutions for or even pay large amounts of money in licencing for (SAP, PeopleSoft, etc). BCS brings the ability to present data located in other systems into SharePoint. A tool that many understand and use daily. In this presentation I discuss using Business Connectivity Services within SharePoint Online as opposed to on premises. You can find the slide deck here. Thanks for attending my session on this topic.
Thanks for reading!!
Hi recently had the privilege to do another presentation with Joanne Klein. This time we built a presentation off of a post that she had written around whether we should use flat or deep structures with our site collections and sub sites or if we should have something in between when designing a SharePoint site architecture. It was a lot of fun and we probably could have done entire presentation on just a portion of it. Either way, I promised our attendees that I would post our slide deck. You can find the slide deck here. Thank you very much to everyone who attended.
Thanks for reading!
I recently had a need to read data from an xml configuration file that was stored within a SharePoint library. To make things easier I of course went to Google (or Bing) and checked to see if someone else had yet blogged this. Couldn’t find anything, so in order to help out someone else that may need to do the same at some point, I wrote up a quick little blog. Note: this will only work for on-premises versions of SharePoint. I’ll update with a SharePoint Online version in the future. I’ll also write up how to add and delete contents in a future post as well.