I was preparing a demo for the Arizona SharePoint Pros group on Microsoft Teams, PowerApps, and Flow, and I thought it would be cool if I could have my PowerApp post a message to a channel conversation for teams. After a bit of digging I got it to work. It is fairly simple to setup so I figured I would write this post to make it easier for others to setup. Continue reading “Post to Microsoft Team from Flow”
After writing the Modern Development Lifecycle article I came to the realization that the article I mentioned for creating the client id and secret missed an important step. It missed how to create the application itself. So in this article we are going to create and permission an add-in so it is ready for our use. Continue reading “Manually Registering a SharePoint Add-In”
In big news on the SharePoint development front, the SharePoint Framework reached release candidate 0 yesterday. What does this mean? Release candidate means that what we are seeing now in the SharePoint Framework is pretty close to what it’s going to look when it reaches general availability(GA). In looking through the release notes associated with this release, https://github.com/SharePoint/sp-dev-docs/wiki/Release-Notes-RC0, there are quite a few changes. Some of the changes are pretty major and will break any existing web parts that you may have created. So why would Microsoft do this? The reason is to perform some final cleanup of things that did not exist as they should in a polished project. They had to rename and move quite a few things. If Microsoft did not do this now it would probably not happen and there would be areas of conflict and confusion. You can tell the scope of how many different areas have changed by the update steps that are included in the release. Previous releases had a couple things that needed to be updated, while this release has 12 different steps of things that need to be updated. If you are doing SharePoint Framework development I highly suggest that you look through the release notes. The release notes will guide you through all the changes and Microsoft’s direction and thinking about the changes. Some of the most notable changes are:
I am announcing the initial release of my first open source project, AngularSP. I have been working more and more with AngularJS and I love it. AngularJS has saved me so much development time. The problem I saw was that every project I worked on, I had to embed/re-create the connections with the SharePoint REST services. I kept thinking, I really should just do a service similar to $http to encapsulate the functionality. So here is the initial release of the factory. Currently the library handles all of the CRUD operations on SharePoint lists hosted within the same domain as the calling page(no cross site calls as of right now, that will come later). The library will work with On-Premise SharePoint as well as SharePoint Online in Office 365. The plan is to add more functionality as time goes on.
The current priorities are listed on the CodeProject site but I am including them here as well for now.
Automatic handling of Request Digest Token for RESTImplemented
- Search Calls
- All implemented methods for the request executor.
Let me know if there are any features that you would like to see added.
Presented a successful session on Office 365 at SharePoint Saturday in Denver.
Office 365 Public Sites are one of those features that I have mixed feelings about. It was an awesome selling point with client to be able to say, “Buy Office 365 and you get your public site for free.” At ITG we have several clients where we have setup their public site and for the most part it works, as long as you are not expecting full SharePoint functionality. At ITG we have had several discussions about what the best approach would be for our customers that a full ECM solution for their public site since the Office 365 public site didn’t give them that. Well we don’t have to make that discussion anymore, thank you Microsoft.