Cross site collection navigation
Current term set based solution is not usable at all in real life multi site collection scenarios.
SharePoint hub sites ,which shipped earlier this year, provide a configurable cross-site navigation control. More information: https://techcommunity.microsoft.com/t5/Microsoft-SharePoint-Blog/Organize-your-intranet-with-SharePoint-hub-sites/ba-p/174081
For questions, please reach out via the SharePoint Techcommunity: https://techcommunity.microsoft.com/t5/SharePoint/ct-p/SharePoint
For any additional features, please search for or open new UserVoice suggestions.
22 commentsComments are closed
J pike commented
Yes this is preventing us from rolling out our new corporate intranet built upon Modern site collections. No global nav renders the OOTB components worthless as a larger solution Help!
and please hide any site collections from the navigation which people don't have permission to (like within a site collection with navigation to subsites).
Kyle Petersen commented
Just saw the Ignite sessions on Hubs. This looks promising. Looking forward to seeing this on my "targeted release" tenant.
Any News from Microsoft since over 1,5 years?
I get why global navigation is wanted. Currently though, we're planning to just go with "Sharepoint Home" and let that be it. We'd really like more control over that page, however. For instance, we would really like a list of all the sites you can access, as well as the ability to organize it a little bit in a sort of treeview or other hierarchical construct.
Ernest Correale commented
This has been a pain in the neck since the beginning. There are so many of these "little" issues with SharePoint that we have really begun to look for alternatives. It's just a pain in the ass to do anything with SharePoint.
Star D. commented
Out of votes, but strongly support this idea.
Andrew Walman commented
We tried using the multi-termset/termset pinning idea to use friendly URLs across site collections (with a mega-menu), but you end up with a nasty error page when you navigate between site collections. Having a solution that uses termstore navigation would also solve the problem of being unable to easily rename site collections, and the limitation of only two site collection paths. PnP does have some great APIs for managing the termstore, but that's no good if the termstore can't work across site collections!
Sean Whyment commented
This is one of our main headaches at the moment as we prepare to implement SharePoint for our new intranet, as from reading replies on this and other threads existing HTML/CSS/JS solutions to implementing global navigation seem to not work with the new look SharePoint experience.
A built-in global navigation function which works across sites and site collections with some basic styling options would be ideal.
Microsoft needs to make this easier for their non-technical customers, IMO. Being able to only do it with sub-sites right out of the box seems like it's only half-done.
Hassan Syed commented
We employed a different technique to address
1. Cross site collection browsing using Js, HTML and Css
2. Enabling it on the new look pages (the solution works fine in the classic view).
We developed multiple versions of FlyView for SharePoint http://fly-view.com. It is a responsive menu that allows you to navigate across multiple site collections.
Since the server version is waiting on Microsoft to roll out customisations support therefore we implemented this functionality in our browser plugins for Chrome and IE and they work even on the New Look Pages.
Other vendors can also look at the browser plugins as an alternative for supporting New Look pages till Microsoft provides the support for New Look customisations.
Brent Ellis commented
Had our custom responsive megamenu working flawlessly in a modern doc lib and site contents site until build version 16.0.5409.1204 rolled out and Microsoft disabled ScriptLinks across the board....
Would push down the body 35px or 50px and float a div on top of it, then inject the menu html into that div.
But alas, can't use it anymore :(
Scott Brickey commented
MS : the approach I've taken is:
1. Start with a sitemap, extend spec to support pattern matching of site collections (usually based on managed paths), and displaying subsites (via sitemap hierarchy, which is rendered by the various providers and asp:menu controls)... I used something along the lines of <url>?SPSite=1&SPWeb=1 for including collections and subsites... though a service app with a custom SPDatabase would make more sense for several reasons, at which point the SC/SubSite options are just fields.
2. SecurityTrim then cache the results.
3. Feature scoped to WebApp : take over top nav... apply the sitemap provider with a higher priority than that of SPF/teamsite or SPS/topnav... disable links in Site Settings
4. Feature scoped to SPSite : same as above, just scoped differently
the webapp scope can be used by farm admins to enforce global nav to all SPSites, such as may be the case with smaller intranets, or external portals. the SPSite scoped feature can provide an "opt-in" approach.
the only real "bug" was that creating subsites offered users with false hope of breaking inheritance of topnav... a bug that has generally been acceptable to the users.
additional scope creep:
- probably not a bad idea to have a feature stapler to some core feature, so that new site collections can be "registered" into the service app database, which would probably be a ton faster lookup than iterating through the webapps' spsites... with such a lookup, it'd be easy to then parallelize the impersonated SPSite instantiation for security trimming, and to grab the SPSite.AllWebs.Urls
David White commented
One solution which almost works well! is to have a master termset navigation with the links common to all site collections. Create a termset for each of your site collections and pin from the master termset. All works well until you change or add anything to the master as the changes do not ripple down as expected and you have to re-pin
Please keep in mind that enterprise customers often have multiple SharePoint farms, plus Office 365. New navigation should not be limited to single farm
This is really a bummer when you try to build a bigger site w/o custom navigation (which is what MSFT is wanting us to get away from, right? So they should fix this). Especially that you can synch the labels of pinned terms, but not their URL is not synched is just half-baked
Agree that it is unbelievable that there is no such thing as a global nav
Gideon Mulder commented
Yes and security trimming within a web application or the posibility to split content databases per spweb.
Paulo De Almeida commented
A navigation term set cannot be reused in other site collection since it's already used once... so this is definitively not a good solution and it must be improved ! I agree 200%