SharePoint Musings

In recent travels I've encountered what seems to be either a product limitation or a bug. After digging around some it appeared that I wasn't the only one facing this challenge, and unfortunately there wasn't a concrete enough solution or workaround out there. Hence the blog post hoping to save some of you the unnecessary hair-pulling which I had to endure. My task was fairly simple; "Start a Site Workflow using a Custom Action button". The first part, creating a Custom Action, is trivial. This can be done in Visual Studio or SharePoint Designer. For the sake of simplicity I used SharePoint Designer. Create a Custom Action button Start up SharePoint Designer 2013 and connect to the desired site. From the left navigation select Lists and Libraries. I'm using a simple list called "List One". Boring name, but easy to follow. :) Click on the list name to manage list settings. From the ribbon select Custom Action button then click View Ribb

Introduction At some point you probably thought about incorporating glossary functionality as a part of a larger solution, or perhaps you were simply looking for providing a more intuitive way of filtering hundreds of items within a List or Library. Now there are countless web parts out there that you can either purchase or download from the SharePoint Store free of charge, and they all come with their own set of bells and whistles.  However, if you are looking at building one yourself, well look no further. To accomplish this we will need three major ingredients: SharePoint Page (either Wiki or Publishing will work) SharePoint List/Library with some content (Files/Items) HTML Form Web Part Let's Implement In this post I’m using a simple Wiki page, but you can also use a Publishing page as well.  We just need a canvas to display our glossary. I presume you already have a list or library that contains some content which is applicable to this concept.  I’m

If you are a SharePoint administrator looking to quickly apply some basic branding to a site-collection in your SharePoint 2013 environment then you've come to the right spot. Before we begin I assume you have a basic understanding of what Composed Looks are, and perhaps you spent some time playing around with this concept in SharePoint 2013. If not, then don't worry.  Here is a basic primer: Composed Look is basically a package which contains elements used for controlling the overall look and feel of a SharePoint site.  This includes but not limited to Colors, Fonts, Background Image, CSS files, and Master Page files. Once created, Composed Look can be packaged by using the Design Manager feature, or we can use PowerShell to apply it across one or multiple site collections. NOTE: In this post we will be focusing on creating a composed look from an .spcolor file then using PowerShell to apply the design to a site-site collection of our choice.  We will not

I ran into a snag the other day after publishing an InfoPath form (as a Content Type) to one my SharePoint 2013 sites.  I was able to successfully publish the form to the Form Templates library.  Next step was adding the form to the page using the InfoPath Form Web Part. Problem When attempting to configure the Web Part I ran into this: The message clearly states that "No lists or libraries with InfoPath content types can be found." Solution Please check the following depending on how you published the InfoPath form within your environment. When publishing InfoPath form as a Content Type: See that the InfoPath form is being published to the same site as where the page with InfoPath Web Part is. Make sure that the Library (Form Templates) where the form is being published to has Content Types enabled. Enable Content Types on the Form Library where the form is submitted to (I'm assuming you are using a Forms Library other than the one in Step 2 for thi

Ever wondered what features were included in SharePoint Server Enterprise but not in Standard?  How about feature sets native to SharePoint Server versus SharePoint Online? Well fear no longer my fellows! :) Compliments of our dear friend and SharePoint MVP Andrew Connell, the following is a list of features broken down by Audience (Developer or IT-Pro) and Workloads.  You can check out AC's blog right here:  Andrew Connell Blog You can download the full file containing Office 365 and SharePoint Online here: SharePoint 2013 Feature Comparison Matrix Audience Workload Features Foundation Server Standard Server Enterprise Developer Access Services NO NO YES Developer App Catalog (SharePoint) NO YES YES Developer App Deployment: Autohosted Apps NO NO NO Developer App Deployment: Cloud-Hosted Apps NO YES YES Developer App Deployment: Share