Tag Info

Hot answers tagged

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 ...


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. ...


3

You cannot create Site Collection specific Term Stores, but you can create Site Collection specific (local) Term Sets. Details here.


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

According to a few articles, not all types of columns are available/supported via REST in SharePoint 2010, including managed metadata columns. Not Supported Managed Metadata Managed Metadata (Multi) Publishing HTML Publishing Hyperlink Publishing Image Media Field Summary Links Publishing Image Source: ...


2

You can put the specific term store name in the Site property bag and in the feature receiver fetch it from there.


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 ...


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

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

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)


1

Recently I found solution for this problem by myself. Problem was with attribute ControlId="QuickLaunchDataSource", that was overriding part of my attributes in SiteMapDataSource. ControlId is a part of navigation feature,that stores settings in NavigationSiteSettings.xml It is located in C:\Program Files\Common Files\microsoft shared\Web Server ...


1

Here is what i did to have a treeview. Certainly not the best method but a working solution Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue $url=Read-Host "Entrez l'url du site sharepoint" $siteCollection = Get-SPSite $url $web = Get-SPWeb($url) $termSet = Get-SPTaxonomySession -Site $url $termStore = ...


1

Have a look at the TaxonomyItem.NormalizeName method Try changing your code to Term trm = trm1.Terms.GetByName(TaxonomyItem.NormalizeName(parentName));


1

Here is an excellent article that outlines many options Synchronize, Import or Copy Term Stores & Managed Metadata in SharePoint Between Environments Which is best for you depends on your exact requirements. For my requirements I found number 5, the PowerShell cmdlets by Gary Lapointe/Aptillon to be very good. It can export/import most things ...


1

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

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.


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

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

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

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

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

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

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

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

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

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

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

Basically it depends on the following settings: a Default Language of Term Store selected language while creating Term Set Assume English(1033), Finnish(1035) and Russian(1049) languages are installed and the following code is used for retrieving term sets: var ctx = SP.ClientContext.get_current(); var taxSession = ...


1

It would be nice to see, how (I mean, from which context) you receive your term in the MyMethodToGetTerm method, and how do you try to add / update it later. You wrote, you can add terms, but not update them, however it is not clear from the code, how you try to achieve that. You should get and update the Term in an elevated context you receive via code ...


1

I have been looking for the answer to this one too. The following should retrieve the extra properties: //paste code on one line context.load(tsTerms, 'Include(IsRoot, Labels, TermsCount, CustomSortOrder, Id, IsAvailableForTagging, Name, PathOfTerm, Parent, TermSet.Name)'); The following blog had some good examples that have helped me get my code ...



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