Tag Info

New answers tagged

0

In addition to @Dylan's answer following are the UI settings which affects setting of this properties: DefaultSiteCollectionTermStore Maps to the default proxy of Managed Metadata service. If there are multiple proxies,only one proxy has to be designated as default else this property will return NULL DefaultKeywordsTermStore maps to the configuration check ...


0

The DefaultKeywordsTermStore is a global term store that contains enterprise keywords. The DefaultSiteCollectionTermStore is a term store that has metadata local to the site collection. Here is the MSDN documentation on the TaxonomySession class which defines those two properties of the TaxonomySession object. Here is the MSDN general overview of Managed ...


0

The issue in this case was a version mismatch between the referenced Microsoft.SharePoint.Client.dll and the SharePoint Server version. The DLL file was the RTM version (15.0.4420.x) while the server was on Service Pack 1 (15.0.4569.1000). After updating the reference, it worked as expected.


0

Had this problem. Creating a new web app, importing terms to term store and session is null. Solution was to open a new powershell session and ran my termstore related commands.


0

Turns out I was using the wrong web part. 'Content Search' web part is the one I needed. This is now less confusing.


1

it's impossible from out-of-the-box, but you can use 3-rd party solutions. For example from VirtoSoftware (link) , BambooSolutions, or SharePoint Boost. Also you can upload multiple files with predefined properties (managed metadata supported) with Bulk File Upload.


0

Start here. It speaks to using Term sets for global navigation. Overview of managed navigation in SharePoint Server 2013 https://technet.microsoft.com/en-us/library/dn194311%28v=office.15%29.aspx#section1 You can find step by step instructions here: ...



Top 50 recent answers are included