none
MaximumDynamicDisplayLevels not working RRS feed

  • Question

  • Hi Guys,

    I have the same setting for 2010 and 2013 for the flyout nav, in 2010 it works in 2013 it shows no > arrows.

    If i change the StaticDisplayLevels it works as expected, but i am trying to get

    subiste -> subsite 1

                         -> subsite 1a

                 -> subsite 2

                        -> subsite 2a

    has anyone got this working in 2013?

    	<asp:ContentPlaceHolder id="PlaceHolderTopNavBar" runat="server">
    		<SharePoint:AspMenu
    			ID="TopNavigationMenu"
    			Runat="server"
    			EnableViewState="false"
    			DataSourceID="topSiteMap"
    			AccessKey="<%$Resources:wss,navigation_accesskey%>"
    			UseSimpleRendering="true"
    			UseSeparateCss="false"
    			Orientation="Horizontal"
    			StaticDisplayLevels="2"
    			AdjustForShowStartingNode="true"
    			MaximumDynamicDisplayLevels="4"
    			SkipLinkText="" />
    	</asp:ContentPlaceHolder>
    


    InfoPath MVP | SharePoint 2010 MCITP & MCPD | Office 365 MCITP | CUBE4 SharePoint Blog | InfoPathTips.com

    Wednesday, December 5, 2012 12:34 AM

Answers

All replies

  • I am going to give it a try to see if I can get it working.

    One thing I noticed is that Microsoft added the StaticDisplayLevels property to Microsoft.SharePoint.WebControls AspMenu class in SP2013 http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.webcontrols.aspmenu.staticdisplaylevels.aspx whereas before it used to inherit the property from System.Web.UI.WebControls Menu class (http://msdn.microsoft.com/en-us/library/ms412476(v=office.12).aspx). My guess is that they had to do that to make it work with some of the other properties they added in SharePoint 2013. But what is strange is that MaximumDynamicDisplayLevels still appears to inherit from System.Web.UI.WebControls.

    My guess is that there is a bug, but I am going to give it a shot


    Doug Hemminger http://www.sharepointdoug.com

    Tuesday, December 11, 2012 4:34 AM
  • I tested this out and was not able to get it working. I updated the master page on an OOB Team Site with several sub sites (and sub sub sites and sub sub sub sites). Fiddling with various properties and settings also did not help. Based on my previous comment and the results of my own test, I would guess that this is a bug.

    Doug Hemminger http://www.sharepointdoug.com

    Wednesday, December 12, 2012 4:10 PM
  • Hi,

    I am having same issue. Whatever number I specify in MaximumDynamicDisplyLevels it does not show up more than one 2 levels. Has anyone find out any workaround?

    Thanks,

    Dhaval Patel


    Dhaval.A.Patel

    Thursday, December 13, 2012 4:38 PM
  • Hi, same result for me, the MaximumDynamicDisplyLevels don't work as it did in SP2007/2010 and the same goes for the quicklauch that uses the sharepoint aspmenu. No matter if you remove this property or change it's values.
    / C

    Blog: chrisstahl.wordpress.com Twitter: @Cstahl

    Tuesday, December 18, 2012 10:55 AM
  • does anyone know how we can log/escalate this?

    InfoPath MVP | SharePoint 2010 MCITP & MCPD | Office 365 MCITP | CUBE4 SharePoint Blog | InfoPathTips.com

    Thursday, December 20, 2012 5:07 AM
  • Same issue for me, need to report this to MS..
    Friday, March 15, 2013 3:27 PM
  • Got the same issue. Also interested in a solution or workaround. 

    - Dennis | Netherlands | Blog | Twitter

    Tuesday, March 19, 2013 3:06 PM
  • Any news on this issue would be grateful..

    //Martin

    Thursday, March 21, 2013 6:08 AM
  • Hello Martin,

    Just got a tip from a colleague to try the oslo.master instead of the seattle.master. With oslo.master the MaximumDynamicDisplayLevels are shown. Now in the process of comparing the two masterpages.

    Btw, in the oslo.master it actually is the aspmenu with id V4QuickLaunchMenu, that one is presented horizontally. Sorry for the confusion.

    Hope this helps a bit.


    - Dennis | Netherlands | Blog | Twitter


    Friday, March 22, 2013 11:00 AM
  • Hello Dennis,

    Ok, to bad I don't like the oslo.master.. :)

    Well let us know if you find something that could get it to work on Seattle.master.

    regards

    Martin

    Friday, March 22, 2013 12:03 PM
  • Hello Martin,

    Will do.

    Btw, which version are you using of SharePoint 2013? I can reproduce this on build 15.0.4420.1017.


    - Dennis | Netherlands | Blog | Twitter

    Friday, March 22, 2013 1:09 PM
  • Dennis,

    thx m8

    we are running on SharePoint 2013 15.0.4420.1017

    Regards

    Martin

    Friday, March 22, 2013 1:13 PM
  • @Expiscornovus I think you edited your post, you're saying the quick launch menu works but the horizontal menu still doesn't respect the displaylevel settings?

    Tuesday, March 26, 2013 4:20 PM
  • @Jeremy @Dennis,

    As I understand it is only the Top Navigation that is the problem here with horizontal flyouts, and as I understand your edit to the post is that oslo.master uses the quick launch as main navigation as for the seattle.master uses top navigation that no one still has any idea how to get it to work?

    //Martin

    Tuesday, March 26, 2013 8:28 PM
  • @Martin @Jeremy

    Martin is correct with his statement above :) 

    My findings are that the MaximumDynamicDisplayLevels property works with the QuickLaunch and not with the Top Navigation menu. This is confusing because in the Oslo masterpage it actually uses the QuickLaunch as main navigation.


    - Dennis | Netherlands | Blog | Twitter

    Wednesday, March 27, 2013 7:50 AM
  • @Dennis,

    We have to hope for an fix from Microsoft soon then, has anyone tried the March Update if this has been solved?

    //Martin

    Wednesday, March 27, 2013 7:53 AM
  • @Martin

    We could also reproduce this on Office 365, so I guess that environment has the March bits. We were only able to reproduce it with the structural navigation though. So maybe the managed navigation setting is a good workaround for you?

    Today I also got together with a colleague (developer) for another workaround, because structural was our desired setting for the Global Navigation. We ended up implementing our custom sitemap provider in order to get the MaximumDynamicDisplayLevels property working.

    Btw, with .NET Reflector we did some analysis and found a property called MaximumSupportedNodeDepth (which was set to 3) and a method called AdjustForProviderMaximumDepth. From the looks of those findings it looked a bit more by design instead of a bug.  But that's just my 2 cents :)


    - Dennis | Netherlands | Blog | Twitter

    Wednesday, March 27, 2013 8:49 PM
  • @Dennis,

    we had already tried the manage navigation, which btw worked with multiple levels and flyouts, but found the limitation in the meta navigation to be that there is no audience so even if you have not access to a team site the link will be visible in the navigation, people with just read permissions on the site will not be able to see the navigation, somehow a member needs add or edit permissions in order to view the navigation..

    It is a nice feature, but I guess it is more for publishing sites towards customers and not so much for intranet site that we us SP2013 for..

    Thanks for the update m8, for now I solve the issue by changing the quick navigation layout for a user to drill down in the navigation until there is a fix for this issue.

    Keep me posted. :)

    //Martin

    Wednesday, March 27, 2013 9:18 PM
  • We're on March CU and it still doesn't work.

    Configuration database version:
    15.0.4420.1017

    Configuration database server:
    sp2013

    Wednesday, March 27, 2013 10:33 PM
  • Some of my Office 365 clients were recently upgraded to SP2013 behind the scenes (even if the site collection upgrade wasn't performed) in one case, the 2nd flyout menu level was working fine, and suddenly stopped working after the upgrade. It is now limited to a single level. I opened a thread on the Office365 community site on this topic.

    http://community.office365.com/en-us/forums/154/p/154413/433287.aspx#433287


    Nikolas Charlebois-Laprade Microsoft Certified Professional Software Engineer and Senior SharePoint Advisor http://nikcharlebois.com

    Friday, April 5, 2013 12:03 PM
  • I am having exactly same problem.

    Here is what I found:

    MS has a  MaximumSupportedNodeDepth= 3 in PortalSiteMapProvider

    and this value is used in AspMenu control AdjustForProviderMaximumDepth() to reduce the MaximumDynamicDisplayLevels.  

    Not sure why??

    Friday, April 5, 2013 6:23 PM
  • @Wei_Wang

    I agree, like I said in my previous reply the AdjustForProviderMaximumDepth method is an interesting one.

    It actually also uses the StaticDisplaylevels property value for the calculation too :)

    @Martin

    Did you get in contact with Microsoft about this? Otherwise I will give that a try :)


    - Dennis | Netherlands | Blog | Twitter

    Saturday, April 6, 2013 8:23 AM
  • @Dennis,

    No sorry, I tried, but do not know where to start, I have been busy trying to work around this issue.

    But please give it a try to contact Microsoft about it.. :)

    //Martin

    Monday, April 8, 2013 8:18 AM
  • Hi there,

    do you have any news or even a solution to this Problem?

    I also have a customer who got updgraded and now faces the same issue.

    Regards

    Julian

    Tuesday, April 16, 2013 9:10 AM
  • We have opened a Microsoft Support Case and it is a confirmed Bug and should be fixed in the August CU
    Tuesday, April 16, 2013 11:40 AM
  • Great, but what about Office 365? We have the same problem since they upgraded the servers.

    Nikolas Charlebois-Laprade Microsoft Certified Professional Software Engineer and Senior SharePoint Advisor http://nikcharlebois.com

    Thursday, May 23, 2013 10:47 PM
  • Hi Nik,

    I'm having the same issue as our hosted sharepoint on 365 has just been upgraded. Jumping into your community thread to push for an answer!

    Jon

    Thursday, June 20, 2013 8:57 AM
  • What about using the GlobalNavSiteMapProvider instead? I tried it and it returns the same thing as SPNavigationProvider except that it includes the sub-sites (which makes 2nd lvl flyouts work). Could someone tell me what the difference is between the two? Thanks!
    Tuesday, July 2, 2013 9:03 PM
  • @Jeremy 15.0.4420.1017 is RTM bits - not March CU.

    I can confirm that it works with 5 levels (four flyouts) in march and april CU (I'm using managed navigation).


    • Proposed as answer by klinkby Thursday, September 5, 2013 1:01 PM
    • Edited by klinkby Thursday, October 3, 2013 12:59 PM
    Monday, August 19, 2013 12:19 PM
  • Hi,

    August CU is out and seems to fix this issue: http://support.microsoft.com/default.aspx?scid=kb;EN-US;2817616

    br,

    -hk

    Tuesday, August 20, 2013 11:40 AM
  • Hi everyone,

    I can confirm that the August 13, 2013 CU fixed the structured navigation issue.

    As HK mentioned, you can learn about the fixes including in the August CU as well as get a link to the CU at:

    http://support.microsoft.com/kb/2817616/en-us

    Although this is a cumulative update that includes previous fixes, there is a prerequisite. You must first download and install the SharePoint Server 2013 update from March 12, 2013.

    http://support.microsoft.com/kb/2767999/en-us

    I found that a reboot was required for each update even though the documentation did not state this. These updates were both ~1.5GB downloads and took about 4 hours to install (each) on my dev env. There is a blog on how to speed up the CU installs at http://blogs.msdn.com/b/russmax/archive/2013/04/01/why-sharepoint-2013-cumulative-update-takes-5-hours-to-install.aspx. I have not tried this myself but may be worth a look.

    In my test env I created a site with five levels and I was able to display 2 levels of static and 3 levels of dynamic navigation without any problems.


    Eric Overfield - PixelMill - blog.pixelmill.com/ericoverfield - @EricOverfield

    Wednesday, August 21, 2013 3:41 AM
  • Nah. Tried on 365 version SR | 16.0.0.2016. Still not working.
    Thursday, October 3, 2013 10:08 AM
  • Any news about this issue?
    Wednesday, February 5, 2014 5:54 PM
  • Seems like it still the same even after SP1. Still not working.

    /C


    Blog: chrisstahl.wordpress.com Twitter: @Cstahl

    Monday, March 24, 2014 8:38 AM
  • Just to give an update. In our case it worked with the August 2013 CU for SharePoint 2013.

    The kb article also describes this bug fix:
    http://support.microsoft.com/kb/2817616

    Assume that you add a hierarchy of sub-sites to a SharePoint Server 2013 site on which the Publishing Infrastructure feature is enabled. In this situation, navigation hierarchies do not display more than two levels in the left nor top navigation controls.


    - Dennis | Netherlands | Blog | Twitter

    Wednesday, April 30, 2014 8:49 AM
  • Great, I can also confirm that this works in SharePoint Online at the current time.

    / C


    Blog: chrisstahl.wordpress.com Twitter: @Cstahl

    Wednesday, April 30, 2014 8:58 AM
  • Howdy - we have applied the Dec 2013 CU, but only the main site is able to view flyouts beyond 2 levels! Does this mean that all sites/sub-sites will need to have the master page tweaked? Not cool!
    Wednesday, July 30, 2014 5:56 PM
  • I would verify that your sub sites are still inheriting their master page from their parent through the entire chain. If you purposely did not want sub webs to inherit their master page, then check to make sure that the MaximumDynamicDisplay property is set to >= 2 in the master page a particular subweb is accessing.

    Also, make sure that a particular subweb is configured to inherit the top menu correctly. Do you have each subweb set to use the same top nav as its parent?


    Eric Overfield - PixelMill - blog.pixelmill.com/ericoverfield - @EricOverfield

    Thursday, July 31, 2014 9:36 PM