SharePoint 2013 top link bar extended dropdown RRS feed

  • Question

  • Hello,
    In SharePoint 2010 it was easy to configure an extended (1 level deeper) dropdown menu by editing the "MaximumDynamicDisplayLevels" in the master page.
    In SharePoint 2013 some things have changed. So, I've edited the "MaximumDynamicDisplayLevels" the HTML Master Pages (in my case seattle.HTML). Unfortunately nothing changed in my SharePoint 2013 environment.
    Can anyone help me?
    Friday, March 8, 2013 12:38 PM

All replies

  • Hi ,

    Thanks for your post, this is a known issue recently.

    You can try with the Managed Navigation per the following article as a workaround.


    Daniel Yang
    TechNet Community Support

    Thursday, March 14, 2013 10:42 AM
  • Thank you. The Managed Navigation is certainly a solution to create the extra dropdown, but isn't an option for me, because the sites are created and deleted all the time.

    I've submitted this question at Microsoft, and they are looking into it (I'm the first one which is reporting this problem at Microsoft). If anyone has a solution in between I'm happy to hear about it.

    If Microsoft offers me a solution, I will let you know.

    Thursday, March 14, 2013 11:03 AM
  • Hi,

      Having the same issue and I'm glad that this is finally addressed as a know issue.  The Managed Navigation is not an option in our case due to the lack of security trimming on links...

    Any workarounds ?

    Monday, March 25, 2013 8:04 PM
  • I'm using SharePoint online 2010, and navigation was working fine, suddenly starting last week the SharePoint designer didn't open the site giving message different versions are used from online to designer, so I installed designer 2013 to check if it will work and yup its working....

    the problem is when this happened the top navigation bar stopped showing the second level in dropdown menu as well.

    is this a Microsoft bug or I have to do something?....

    first of all this should not be happening.. the site was working fine and Microsoft decided to upgrade the 365 to SP2013 and now we are facing the problem.

    please advice how to fix this problem

    Monday, April 1, 2013 11:09 AM
  • @844f69bb-b194-4e8b-8340-83a86db4b70f

    Did you end up getting a work around or date when we could expect a fix for this? We are experiencing the same issue and this might actually halt us from going live with our 2013 upgrade.

    • Edited by Jarner7 Friday, April 5, 2013 3:16 AM
    Friday, April 5, 2013 3:02 AM
  • Please keep me posted on this as well.  I'm having the same exact issue.  Thanks!
    Monday, April 8, 2013 7:47 PM
  • I' am also waiting for a solution for this Problem.

    Please let me know if you have found one :-)

    Monday, May 6, 2013 9:10 AM
  • Hi All.

    This is registered as a bug with Microsoft and according to the thread below, it should be fixed in the August CU.
    The info is only secondhand info, but it seems credible.
    Same behaviour is present in Office 365 which will increase the odds of Microsoft beeing eager to fix it. (last post from Daniel Schnyder)

    Best regards

    Thomas Balkeståhl - Technical Specialist - SharePoint -
    Download 'The SharePoint Branding Project' here
    Download 'The final guide to Alternate Access Mappings' free whitepaper here
    Download 'The final guide to SharePoint 2010 Site Settings' free whitepaper here
    Download 'The final Kerberos guide for SharePoint technicians' free whitepaper here

    Wednesday, May 15, 2013 1:32 PM
  • I have applied the August CU and changed the MaximumDynamicDisplayLevels to 4 and still can't add a third level. As any other master changes required to make this work. I have a team site template with publishing turned on and I have a subsite e levels down, list this: /level1/level2/level3. I want level three subsite to appear on the top navigation menu. THANKS!










    StaticDisplayLevels="2" AdjustForShowStartingNode="true" MaximumDynamicDisplayLevels="4" SkipLinkText="" /> </asp:ContentPlaceHolder>

    Kathryn Birstein, Senior SharePoint Architect

    Wednesday, August 28, 2013 7:43 PM
  • Was there ever a solution brought to bear for this issue which is clearly a bug?  Why is a thread this important just left dangling with no one at Microsoft posting info about  CU that fixes it or a bug update?  It's been a few years now...


    Monday, July 20, 2015 2:29 PM