SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a question about the OnQuickLaunch property in SharePoint 2013. I've created a new SharePoint 2013 project in Visual Studio with a document library List instance in it. All I have is an elements.xml that looks like this.

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="">
  <ListInstance Title="List" 
            Description="My List Instance">

I've set the OnQuickLaunch property to true but if I deploy my solution, the list isn't on the quick launch.

Is this a bug in SharePoint 2013, or am I doing something wrong?

share|improve this question

Sorry for posting this as an answer, but I can't post replies yet. :(

I have the exact same problem, only some lists appear under the "Recent" node. I too declare the list to appear on the quick launch the same way, but when I check the list settings the "Display this list on the Quick Launch?" setting is set to no.

I think this behavior is new to SP2013, since I can't remember ever having this problem before.

If someone has a quick fix I'm all ears. Otherwize I guess there are some not-so-good solutions, such as adding a list event receiver for the ListAdded event and setting the property through code. Quite a hassle for something that should just work though.


Actually I think I have an answer now.

Speaking with a colleague of mine, he had the same problem a short while ago. He found that adding the list instance in the onet.xml instead of using a list instance did the trick. Because when adding list instances in the onet, SharePoint uses a different kind of element which has the "QuickLaunchHeading" attribute. This attribute is not present in the ListInstance element. So in the configuration element, you could add lists like so:

        <List Title="MyList"

There are some drawbacks to this though. You cannot be sure of the order in which stuff is provisioned, so you cannot activate a feature which is depending on the list. Just to clarify I haven't tried this yet, so my answer may not be 100% complete, but I will try it soon though. :)

share|improve this answer
Thanks for your tip about the onet.xml. Unfortunately I wasn't able to use an onet.xml in my case. :( – Marlou Mar 7 '13 at 15:57
As it turned out, neither was I. My guess is that it is a new bug for SP2013, or simply a bad decision on Microsofts part. We ended up setting the property in code in a feature receiver after the list was created. – Johannes Mar 22 '13 at 10:36

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.