Hot answers tagged

4

Groups define security boundaries. A group is a set of term sets that all share common security requirements. Only users who are designated as contributors to a specific group can manage term sets that belong to the group or create new term sets within it. Organizations should create unique groups for term sets that will have unique access or security needs. ...


4

You cannot edit the Name directly, because the Name of the TermStore is simply the name of the MetadataWebServiceApplicationProxy. So what you have to do is to rename that one instead. In your example, you have to get the SPMetadataServiceApplication first, find the right proxy and rename it. This should look like this, assumed that your ...


2

You can set property of term set as "Open" which will let anyone add a new term to an open term set. So user not necessarily need to go to the path mentioned above. In list/library while selection of term user can provide new terms as well. (same like allow fill in choices for choice field) refer MSDN


2

Synonyms in Managed Metadata are completely unrelated to synonyms in a thesaurus for Search. You could write a PowerShell script that read the MMS terms and created a formatted thesaurus then periodically Imported/Updated the search thesaurus. In one step traverse your term set and write a thesaurus file in the format: Key,Synonym,Language ...


2

You may need to recreate the Term Set again. Navigate to http://portal/services/_layouts/15/AreaNavigationSettings.aspx directly or navigate through Site Settings: Make sure you have selected Managed Navigation radio button. Click on Create Term Set and check if that solves the problem. Here is my view from the Services AreaNavigationSettings page:


2

The Managed Metadata service application is a different entity and it contains its own database as well. This has its own Users managing provision. Even though you are the Site collection administrator might be you dont have permissions to access managed metadata db. You can have grant the permissions in two levels, when you select the Managed Metadata ...


2

When you create you're the second site collection in your fresh Web Application, it typically comes with additional sites in the URL. It doesn't affect the user unless she wants to type the URL directly. The reason for this as that we use a managed path of wildcard inclusion. With wildcard inclusion, you are able to have as many site collections you want ...


1

I used this workaround. if (!String.IsNullOrEmpty(sortOrder)) { List<string> termGuids = sortOrder.Split(new char[] { ':' }, StringSplitOptions.RemoveEmptyEntries).ToList(); termguids.AddRange(termSet.Terms.Select(t => t.Id.ToString()).Except(termGuids)); foreach (string guidString in termGuids) { // some logic } } ...


1

There was a same question on stackexchange and answered.I hope this article helps you out. How to import term sets to Managed Metadata Service using PowerShell and CSV file Also the below TechNet article explains the CSV file format for metadata termset values. https://technet.microsoft.com/en-us/library/ee424396.aspx However if you have the well ...


1

Microsoft.SharePoint.Taxonomy.Tree JavaScript control (treecontrol.js) is intended for rendering Taxonomy tree control. Microsoft.SharePoint.Taxonomy.Tree PageLimit property defines the number of visible terms. You could consider the following solution to override default (10) PageLimit property value: ExecuteOrDelayUntilScriptLoaded(function(){ ...


1

This is happening because you haven't explicitly requested for Parent Id. Try including that in the load statement 'Include(IsRoot, Labels, TermsCount, CustomSortOrder, Id, IsAvailableForTagging, Name, PathOfTerm, Parent, Parent.Id, TermSet.Name)' You should check whether the current term is root or not as follows if(currentTerm.get_isRoot() == false) { ...


1

Install term set export/import tool WSP from here. Then use the following PowerShell to export and import Term Groups one by one including all content. $ver = $host | select version if ($ver.Version.Major -gt 1) {$host.Runspace.ThreadOptions = "ReuseThread"} if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $null) { ...


1

You can make use of properties Terms or TermsCount. This property provides the list of immediate Terms. So in your case you can use following logic if(term.Terms == null || term.Terms.Count == 0) //means this term has no childern if(term.TermsCount == 0) //means this term has no childern


1

There is no out of the box way to do this. You should use either a workflow or an event receiver. The idea is to handle ItemAdded event or Start workflow on item create or Update. Inside you should remove permission of the item if Term has particular value. Once permission inheritance is broken, you can give permission only to respective users. Note - The ...


1

Here is the other example that you can prefer, SP.SOD.executeOrDelayUntilScriptLoaded(function() { 'use strict'; var nid = SP.UI.Notify.addNotification("<img src='/_layouts/15/images/loadingcirclests16.gif?rev=23' style='vertical-align:bottom; display:inline-block; margin-" + (document.documentElement.dir == "rtl" ? "left" : "right") + ":2px;' ...


1

Unfortunately you cannot import labels using OOB import functionality. I recommend using Lapointe.SharePoint.PowerShell.wsp found here and here to do the import. It supports also labels. You can do first an export to get sample XML out, then modify it, and finally do import. It will not overwrite existing terms (will throw error), so you need want to remove ...


1

The reason your code is not working is that TaxonomySession uses the user from the HttpContext. I found this link which is in German but the suggested code looks like this: var siteId = SPContext.Current.Site.ID; HttpContext oldContext = null; try { //Save actual context and null oldContext = HttpContext.Current; HttpContext.Current = null; ...


1

SharePoint 2013 does not support managing term set using REST API still now. In that case, JSOM is the one and only way. If your requirement is just to read the term set, then you can follow this. module.getTermSet = function (id, callback) { SP.SOD.loadMultiple(['sp.js'], function () { // Make sure taxonomy library is registered ...


1

If you need just a flat list of all terms inside a TermSet you can use GetAllTerms() method. TermCollection terms = termSet.GetAllTerms(); foreach (var t in terms) { Console.Write(t.Name); } EDIT: If you want to preserve the hierarchy , you have to loop through each term as below: TermSet termSet = group.TermSets["MyTermSet"]; TermCollection terms ...


1

Go for the export and import of the term set and then fix the existing items with a PowerShell script. The script should lookup the term in the term store given the text of an old term. Then it should assign the correct term with a new id. Hope it does make sense. I have a PowerShell script for that and if noone else posts an answer, I will upload it here ...


1

Your best bet is using powershell script to export and import the term set as Paul mentioned. Here are script. To Export Add-PSSnapin Microsoft.SharePoint.Powershell $metadataApp= Get-SpServiceApplication | ? {$_.TypeName -eq "Managed Metadata Service"} $mmsAppId = $metadataApp.Id $mmsproxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq "Managed ...


1

Even though the Group Managers description states "Enter user names, group names, or e-mail addresses in order to grant group manager permissions", you cannot use a SharePoint group. From TechNet: SharePoint Group[s are] defined at [the] Site Collection Level while [the] Term Store is defined at [the] Farm Level. Active Directory groups can be used, ...


1

please do the following steps Make sure the service "Managed Metadata Web Service" is started at [Central Admin >> System Settings >> Manage services on server]. If it is not started just start it and wait for some time to get the Service application to take the affect. Make sure the check box "This service application is the default storage location for ...


1

John, All of the examples I've found online tell you to use the Managed Navigation approach. I found a video tutorial and step-by-step instructions that are quite similar. Managed Metadata Navigation in SharePoint 2013 SharePoint 2013 – Navigation using Managed Metadata (Term Store)



Only top voted, non community-wiki answers of a minimum length are eligible