Modern Team Sites and Communications Sites in SP Online - Would like option to use Managed or Structural Navigation
We have an existing portal with managed navigation. Team members would like to use the Modern Team Sites and the new Communication Sites, however these come with their own navigation that can be edited directly on the page.
We are hoping to be able to able to add Managed Navigation and\or Structural Navigation to these type of sites. If publishing could be enabled successfully (at this time it cannot) we would have access to the classic navigation menu.
Cory Wallace commented
Honestly can't believe this isn't a feature. The "newer" way of doing sites (hub and spoke) only has manual navigation? Makes no sense to me.
Renee Barnette commented
Currently I see the following warning for structural navigation in SharePoint Online, Site Settings, Navigation Settings:
(Structural navigation has significant performance impact and is not recommended in SharePoint Online. You can find more details here.)
...and no warning for use of managed navigation with navigation security trimming enabled.
Please update the warning for structural navigation to include stronger/more visible (color, or bolding, or highlighted) text, and the word "Warning"; if possible, make the text in red, at least the word "Warning" in red, something like:
(Warning: Structural navigation has significant performance impact, is not recommended in SharePoint Online, and can contribute to throttling of your entire tenant, affecting functionality and performance of all websites. Read navigation recommendations here.)
For managed navigation, please add a warning to set navigation security trimming to off to avoid risking latency, such as:
(Warning: Managed navigation, while navigation security trimming is enabled, can impact performance in SharePoint Online. If you use managed navigation, it is recommended to disable navigation security trimming. Read navigation recommendations here.)
I ask this because navigation for SharePoint on-premises has worked perfectly fine for many years, and I believe website owners are not aware (and difficult to keep informed distributed across a large enterprise) and may not take the current warning to heart, as they're used to all of the navigation options working fine, and structured navigation had been such a reliable, self-updating, easy to use feature for so many years, on-premises.
We're trying to get the potential issues found on our tenant resolved (after recent resolution of latency, 503 errors, and troubleshooting finding one specifically deeply nested offending site out of thousands), however, even if we were to go through and brute-force change offending/potentially offending navigation - - only the warning would stop any of the website owners from going back and setting it back, especially with turnover in such a large org; keeping uninformed/new website owners from setting new sites to use these navigation types/settings would be difficult.
As long as it's available, and it is such a huge known issue, the warning needs to be made very clear and extremely obvious. I think even a pop-up on selecting them, with a bold warning of potential impact, would be in order, but unless/until that is done, or the option to set these is removed, the quickest way to address the issue would be to have the text updated to be extremely obvious, and very clear that a single website owner's choice to use structured navigation (and the potential issue with managed nav w/security trimming) could cause every website in a tenant to be affected.
*English follows Japanese
[構造ナビゲーション]- [現在のナビゲーション] でリンクの追加を行う際に [新しいウィンドウでリンクを開く] にチェックを入れて設定しても、同じウィンドウ、タブでリンクが開く動作について。
About behavior that when adding links through “Structural Navigation” – “Current Navigation,” links open in the same window or on the same tab despite checking the box “Open a link in a new window.”
[構造ナビゲーション] の設定でビューを含むライブラリ、リストの URLを指定した場合や、ページの URL を ".aspx" まで含めて指定した場合、 [新しいウィンドウでリンクを開く] にチェックを入れて設定しても新しいウィンドウ、タブで画面が開かず、同じウィンドウ、タブでリンクが開く。
このように URL を指定して設定した場合も新しいウィンドウ、タブで開かれるように機能改善を要望します。
When specifying the URL of the library or list that contains a view in the “Structural Navigation” settings, or when specifying the URL of the page that includes up to “.aspx, ” links do not open in a new window or tab even if I select the checkbox “Open a link in a new window.”
I would request an improvement for this functionality so that links will open in a new window or tab when such a URL has been specified.
Daniel Westerdale commented
This seems something that should be part of a release cycle . Otherwise we will all be building custom solutions that do roughly the same thing.
Currently we can’t coordinate the managed meta navigation and the page view like a list by using native function. I think it makes the efficacy for SharePoint Online better if the managed meta navigation and the page view interact mutually.
This is a very important feature for user acceptance. Navigation in out document libraries would be much easier with a tree view feature.
Why does Microsoft downgrade functionalities that are useful and were available in SharePoint 2007/2010?
Paul Frederickson commented
It would be really nice if the exact same navigation options were available on any type of site (even if the default is different).
Dean Henselien commented
Allow Mega Menus to work from managed navigation term set data.
"Hi, we are MS and we are implementing tree structure to modern interface" ... 2 years later: Still missing... Well done MS !
*English follows Japanese
Allow us to use [Open in another tab] feature in Managed Navigation
現在、構造ナビゲーションでは [別タブで開く] 機能が実装されておりますが、管理ナビゲーションでは実装されていないため、管理ナビゲーションでも [別タブで開く] 機能を使用できるように機能追加を要望します。
I would like you to implement [Open in another tab] option to Managed navigation, since it is already implemented to Structural Navigation.
*English follows Japanese
Open link in new window option missing in managed navigation
With structural navigation, link will open in new window, but with managed navigation, open link in new window function itself is missing. Add Open link in new window option in managed navigation
Thank you for your consideration.
Please extend the number of metadata shown in the navigation panel, since I cannot see all the metadata.
Erwin Verlinden commented
I agree, we really need standard support for Open in new window / tab.
Sandra Campbell commented
Any update on this?
We are in the process of moving to the new look and just discovered this is missing. Is going to be painful for our users.
It defies reason that such a core navigation structure such as the treeview was not available at launch, and is still not available a long time after the modern ui release.
Make it happen!
I also am interested in an update
Samuel Levesque commented
If you have an external link and you want it to open in a new window you can't do it using managed metadata navigation. You have to rely on custom JS code or custom navigation.