SharePoint Framework is the new development model proposed by Microsoft to build webparts in modern SharePoint. One question I see alot is, "What about SharePoint Add-Ins? Are they gone?".

For those of you who do not know what a SharePoint Add-In is...it was a new development model for SharePoint 2013 which was meant to replace farm solutions within SharePoint. You can find more information about the SharePoint Add-In Model here (used to be called "SharePoint App Model".

For any of you who are familiar with Visual Studio workflows... you love the added flexibility but you also hate the Workflow Designer and sometimes the activities aren't very clear... Recently I had been working on a workflow for a ticketing system to send emails to members of a SharePoint group.

Anyone who is familiar with my blog will definitely know my slight obsession with SharePoint forms. First it was SPAnyForm, then it was playing around with AngularJS simple forms and now my new obsession of using these forms to generate documents based on metadata from the form or from SharePoint lists.

Exciting news this week as Office Dev center has released the first release candidate version for SharePoint Framework.

Forms have always been a sore subject when it comes to SharePoint. For years many SharePoint environments adopted InfoPath to fulfill their custom form needs. However, this required an Enterprise License, not to mention constant issues with performance, updating content types and and poor branding support.

Even this year Microsoft has decided to end support for InfoPath in 2026 without a replacement. 

Sometimes administrators need to access the SharePoint Access Request list outside of the SharePoint Page.

For those who don't know, whenever a user asks for permission to view your SharePoint site, whether it be access to a file, a team site or folders, that request gets stored in your environment at this location.

There comes a time in every developer's life to make the decision whether or not a piece of software is "good enough" for public consumption. However, I've come to the realization that SPAnyForm-lite will never truly be finished, as it will continue to evolve over time. So here it is!

Happy New Year!

It's been a while since I've been able to update everyone on the status of the SP.AnyForm library. I apologize that I haven't spent enough time finishing up the last touches on the library for public use. With that being said, I wanted to get a version out the public as soon as possible in the mean time. In the next couple weeks I will be releasing a version of SP.AnyForm.js (LITE), followed by a more robust library (FULL) soon there after.

My reason for turning it into two libraries? Beacuase the journey of a thousand miles begins with one step, and this is a great step one. But I have had a TON of interest in the library and I owe it to everyone who has supported me thus far to get a sample in their hands. 

It’s any consultant’s job to build or recommend solutions that are extensible and compatible with future releases and evolving technology. While it’s not always black and white, some of the publicized information regarding SharePoint 2016 has me more confident than ever that the intranet of the future is already here. If you Google SharePoint 2016 you’ll find at least one article with the word ‘Hybrid’ in the title. Microsoft appears (rightfully so) to be pushing to make hybrid deployments easier and 2016 will provide an improved experience. I won’t go into the details since there are a million articles available already, but this does help shed some light on the intranet of the future.

Thanks for checking out part two of my three part blog series on the integration between SharePoint and Sitecore. If you missed last weeks post on my introduction to the topic, you should definitely check it out.

Last time, I gave a pretty quick and high level overview of what "integration" means for SharePoint and Sitecore. There are three types of integration between the two enterprise platforms; page-level, item-level and API integration. For a developer like myself, this is very exciting as the API integration really opens the world for us when creating solutions to extract content between both content management sysems.

In this post I am going to outline the authentication scenarios when integrating the two platforms together.