SharePoint 2013 gives you the ability to use termsets for navigation. When you use the UI (TermStore Management), you can enable a specific termset to be used for navigation by enabling the “Use this Term Set for Site Navigation” option on the INTENDED USE tab of the termset.
If you are used to work with PowerShell and I really encourage people to use PowerShell, you quickly notice that this option is not simply a property on the termset object which you can set to true or false.
The navigation settings are stored in custom properties on the termset. In order to change this setting or to find termsets which are used for site navigation, you need to look for a custom property with the name _Sys_Nav_IsNavigationTermSet.
The script below gives you an example on how you can find all termsets which have this option enabled.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
if ((Get-PSSnapin -Name Microsoft.SharePoint.PowerShell -EA SilentlyContinue) -eq $null) { Add-PSSnapin Microsoft.SharePoint.PowerShell } $adminwebapp = Get-SPWebApplication -includecentraladministration | ? { $_.IsAdministrationWebApplication } $caSite = Get-SPSite $adminwebapp.Url $session = New-Object Microsoft.SharePoint.Taxonomy.TaxonomySession($caSite) $termstores = $session.TermStores foreach ($termstore in $termstores) { $groups = $termstore.Groups foreach ($group in $groups) { $group.TermSets | ? {$_.CustomProperties["_Sys_Nav_IsNavigationTermSet"]} } } |
