SharePoint Musings

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