SharePoint Cross Site Global Navigation

%3CLINGO-SUB%20id%3D%22lingo-sub-89746%22%20slang%3D%22en-US%22%3ESharePoint%20Cross%20Site%20Global%20Navigation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-89746%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20looking%20for%20a%20solution%20that%20leverages%20JSOM%20and%20a%20Managed%20Metadata%20Termset%20to%20provide%20global%2C%20cross-site%20navigation.%20I've%20seen%20a%20%3CA%20href%3D%22https%3A%2F%2Fblog.mastykarz.nl%2Fglobal-navigation-sharepoint-2013-revisited%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Efew%3C%2FA%3E%20%3CA%20href%3D%22https%3A%2F%2Fgist.github.com%2Fcwparsons%2F170be6f8b6a8c253fc46%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Esolutions%3C%2FA%3E%2C%20but%20I'm%20wondering%20anyone%20has%20an%20end-to-end%20solution%20available%20as%20I'm%20not%20that%20great%20with%20JS%20%3A)%3C%2Fimg%3E%20I'm%20not%20looking%20to%20enable%20Publishing%20Infrastructure%20on%20each%20site%20to%20get%20the%20native%20Navigation%20feature%2C%20nor%20do%20I%20want%20to%20have%20a%20termset%20per%20Site%20Collection%20as%20that's%20not%20practical.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20will%20be%20used%20on%20SharePoint%202016.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-89746%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352681%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Cross%20Site%20Global%20Navigation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352681%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20you%20ever%20figure%20this%20out%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-89938%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Cross%20Site%20Global%20Navigation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-89938%22%20slang%3D%22en-US%22%3EWhile%20the%20compatibility%20for%20Core.TaxonomyNavigationComponents%20stats%20SPO%20only%2C%20one%20of%20the%20other%20requirements%20is%20to%20enable%20Publishing%20Infrastructure.%20I%20can't%20do%20that%20in%20this%20environment%20which%20is%20why%20I'm%20not%20looking%20at%20the%20built-in%20managed%20navigation.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-89806%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Cross%20Site%20Global%20Navigation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-89806%22%20slang%3D%22en-US%22%3E%3CP%3Ethe%20solution%20is%20using%20jsom%2C%20and%20with%20provision%20using%20PowerShell%20pnp%2C%20should%20be%20working%20both%20in%20O365%20and%20SP%202016.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-89800%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Cross%20Site%20Global%20Navigation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-89800%22%20slang%3D%22en-US%22%3EThe%20linked%20solutions%2C%20while%20useful%2C%20are%20SPO%20only%20so%20not%20applicable%20here.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-89799%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Cross%20Site%20Global%20Navigation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-89799%22%20slang%3D%22en-US%22%3E%3CP%3Ejust%20some%20thoughts%20on%20the%20topic%2C%20and%20you%20should%20be%20able%20to%20find%20some%20existing%20solutions%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint-Developer%2FSharePoint-Site-Global-Navigation-Mega-Menu%2Fm-p%2F15931%23M505%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint-Developer%2FSharePoint-Site-Global-Navigation-Mega-Menu%2Fm-p%2F15931%23M505%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
MVP

I'm looking for a solution that leverages JSOM and a Managed Metadata Termset to provide global, cross-site navigation. I've seen a few solutions, but I'm wondering anyone has an end-to-end solution available as I'm not that great with JS :) I'm not looking to enable Publishing Infrastructure on each site to get the native Navigation feature, nor do I want to have a termset per Site Collection as that's not practical.

 

This will be used on SharePoint 2016.

5 Replies
Highlighted

just some thoughts on the topic, and you should be able to find some existing solutions
https://techcommunity.microsoft.com/t5/SharePoint-Developer/SharePoint-Site-Global-Navigation-Mega-M...

Highlighted
The linked solutions, while useful, are SPO only so not applicable here.
Highlighted

the solution is using jsom, and with provision using PowerShell pnp, should be working both in O365 and SP 2016.

Highlighted
While the compatibility for Core.TaxonomyNavigationComponents stats SPO only, one of the other requirements is to enable Publishing Infrastructure. I can't do that in this environment which is why I'm not looking at the built-in managed navigation.
Highlighted

Did you ever figure this out?