Content Query Web Part Key cannot be null

Content Query Web Part Key cannot be null

ArgumentNullException: Key cannot be null.
Parameter name: key

Very useful error message!!!! There is a conflict with the Developer Feature in SharePoint 2013 which appears to break the content query web part. Not so hot if you are relying on using this web part on your development site where you need the development feature to be available.

To resolve this issue you will need to disable the feature, unfortunately it is a hidden feature so you will need to disable this via SharePoint 2013 management shell. The powershell script below should help, run this, it will disable the SharePoint 2013 developer feature and Viola you have a working Content Query web part.

------- Start disable developer feature command -------------

Disable-SPFeature -identity  "E374875E-06B6-11E0-B0FA-57F5DFD72085" -URL http://yoursiteurl

------- Endable developer feature command -------------

Once you have configured your content query web part you can re-enable the developer feature if required using the script below.

------- Start enable developer feature command -------------

enable-SPFeature -identity "E374875E-06B6-11E0-B0FA-57F5DFD72085" -URL http://yoursiteurl

------- End enable developer feature command -------------

Hopefully we will see a fix in the next Cumulative update for this issue, I'm sure there will be more. About time for a Friday night SharePINT

Office 365 SharePoint Online Vs On-premises

Microsoft's are ramping up their push towards their cloud offerings with Office 365. Specifically with SharePoint online the Features and services along with the new App Model to deliver a more customisable solution have really closed the gap on what you can produce in an on-premises solution.

One big downfall with SharePoint Online that I have noticed and would love to see available in the future is the ability to add Site Definitions in your custom solutions. Without the ability to add your own site definitions SharePoint Online really is limiting how we can produce tailored solutions to the market, I would love to be able to create a new Team site definition or a new Project site definition that aligned itself to my customers needs without them having to tinker with the configuration of every new site that they create. Along with this feature stapling would be another great benefit to allow the application of design elements, activation of custom solutions etc from any newly created site. If anyone has a cool workaround for these in SharePoint Online send me your comments!

The links below are useful as a reference to identify what limitations there are for SharePoint in the cloud.

SharePoint Online and On-premises comparison of Service descriptions (Navigation links to a breakdown of roles and services)

http://technet.microsoft.com/en-us/library/sharepoint-online-service-description.aspx

SharePoint Online and On-premises comparison of Developer features

http://technet.microsoft.com/en-us/library/sharepoint-online-developer-service-description.aspx

 

If you haven't already seen whats new for developers in SharePoint 2013 check out the link below to see what's on new for you to do!

New SharePoint 2013 on premise developer features

http://msdn.microsoft.com/library/jj163942(v=office.15).aspx

My next post will be available shortly where I'll give you an update on how my study for SharePoint 2013 and Office 365 exams is coming along and hopefully give you a few pointers on what material is out there to help you if you're thinking about SharePoint 2013 certification.