Episode #125 of the Stack Overflow podcast is here. We talk Tilde Club and mechanical keyboards. Listen now
13

It depends on a few basic factors that need to be answered first: Will you use the same term store metadata anywhere else in the farm? You could have project numbers or contacts associated with other site collection in other applications. Maybe not at the moment, but in the future there may be a need. Consider this scenario as you make the decision. Would ...


11

Firstly, you need to know that Managed Metadata Service can be responsible as a Content Type Hub. Content Type Hub is a location where you can manage and publish content type across site collection, web application and farm. One more terminology you need to know is Content Type Subscriber, which will subscribe to Content Type Hub. Once you publish Content ...


10

So, after a few weeks on and off trying to figure this one out, having no luck with any replies on any forum, I just thought I would have a look at how the UI page was doing this. (Why didn't I think of this earlier?!) That's when the property EnableMetadataPromotion showed up. Having this keyword to search for, it didn't take me long to google the missing ...


10

@Ashish Patel answer does not actually work when i tried but i was able to figure it out a bit differently. Here is my version of the helper method based on example provided by code ninja blog, here: private List<Guid> GetTermsIds(SPListItem listItem, string fieldName) { var taxonomyField = listItem.Fields.GetFieldByInternalName(fieldName) as ...


10

a- Add reference to "Microsoft.SharePoint.Taxonomy" assembly b- You need to register following Assembly in your Web Part <%@ Register TagPrefix="Taxonomy" Namespace="Microsoft.SharePoint.Taxonomy" Assembly="Microsoft.SharePoint.Taxonomy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> c- You can use the control as following &...


9

Depending whether taxonomy field is single-valued or or multi-valued use the corresponding method: single-valued taxonomy field: SP.Taxonomy.TaxonomyField.setFieldValueByValue by specifying SP.Taxonomy.TaxonomyFieldValue object multi-valued taxonomy field: SP.Taxonomy.TaxonomyField.setFieldValueByValueCollection Method by specifying SP.Taxonomy....


8

I've recently written a post on how to access Term Store in SharePoint 2013 using the javascript "SP.Taxonomy.js" Hope it helps you. http://cann0nf0dder.wordpress.com/2013/04/09/accessing-taxonomy-term-store-with-jsom/


8

The operation of setting Enterprise Keywords field value consists of two steps: first one to resolve Keyword in Managed Metadata service application (MMS), this what EnsureKeyword method from below example is intended for After Keyword has been retrieved or created if it not existed, the value of Enterprise Keyword field is set to ...


7

Figured it out, might be a Microsoft issue. For some reason, when you set a Navigation Term to "Simple Link or Header" and spell out the URL yourself, the navigation item is viewable to everyone. If you set the navigation term to "Term-Driven Page with Friendy URL" some sort of trimming happens, and only people with write access as well can view the Term. ...


7

I have blogged about it here: http://www.vrdmn.com/2012/12/working-with-taxonomy-and-javascript-in.html The code: $(document).ready(function(){ var scriptbase = _spPageContextInfo.webServerRelativeUrl + "_layouts/15/"; $.getScript(scriptbase + "SP.Runtime.js", function () { $.getScript(scriptbase + "SP.js", function(){ ...


7

Assume the following Managed Metadata fields: Tags (Multiple Taxonomy Field type) NewsCategory (Taxonomy Field type) How to retrieve Managed Metadata field via CSOM in SharePoint 2013 SP.Taxonomy.TaxonomyField value is represented as SP.Taxonomy.TaxonomyFieldValue object: //Get Taxonomy Field value var newsCat = item.get_item('NewsCategory'); var ...


7

It is not possible to use a $filter= and specify a managed metadata field - this is not supported by SharePoint. The only way to filter a REST query using a managed metadata field is to use a CAML query, which requires a POST, not a GET. Since you mention JSON, I assume you are developing it in Javascript. This is a small snippet of code to get you started: ...


7

The following example demonstrates how to get all child terms of a specific parent term using Taxonomy JSOM API var context = SP.ClientContext.get_current(); var session = SP.Taxonomy.TaxonomySession.getTaxonomySession(context); var termStore = session.getDefaultSiteCollectionTermStore(); var parentTermId = '7c43575c-282d-41a3-b20a-f6629bdc4808'; //parent ...


7

When the value in Taxonomy picker control (ScriptForWebTaggingUI) is changed, the event Microsoft.SharePoint.Taxonomy.ScriptForWebTaggingUI.onTextChanged is triggered by default. This custom event could be registered for Taxonomy picker control as demonstrated below: function initTaggingControl() { RTE.CanvasEvents.registerListener(RTE.CanvasEvents....


7

I would suggest Managed metadata.. Increase in list may lead to threshold limit issue. Have look at this article stating pros and cons : MSDN Added benefit to MMS is you can create labels to terms, so it will be convenient for users to type in abbreviations or alternate keywords. Also security can be handled over here.If want users to update or add new ...


6

Our solution was to go to SP Central Admin > System Settings > Services on Server and start the "Claims to Windows Token Service". We also found this error in the logs which helped lead us to this as the solution: SPSecurityContext.WindowsIdentity: Could not retrieve a valid windows identity for NTName='PRMM-SP\polyadmin', UPN='PolyAdmin@PRMM-SP....


6

You cannot completely match the broad feature set of Managed Metadata but you can accomplish a subset of it using the techniques that existed before Managed Metadata was introduced: Define Taxonomic Metadata – Create custom site lists to be used for the management of metadata attributes you want to surface as controlled vocabularies for your site users. ...


6

Ok, this is how I did it: Build a method that enables me to retrieve all items of a certain ContentType (use SPSiteDataQuery for Cross-Site in the same site collection, or simple SPQUery for a single list) - many examples available but look here for a start http://sharepoint-snippets.com/spsitedataquery-examples-for-sharepoint-2010/ (actually i've built my ...


6

It is possible to accomplish with OOTB Metadata Navigation and Filtering Feature using Navigation hierarchies control. Navigation hierarchies control allows to select an item in a hierarchy for a managed metadata column with filter for single Term Term with descendant child terms Applying filter in Navigation hierarchies control corresponds to ...


6

JSOM or REST API = no. BUT you can use JavaScript to call the Taxonomy Web Service to effectively accomplish client-side access. It's definitely more cumbersome than using the CSOM or REST API, though, but it works. Try this out: http://spandps.com/tag/web-services/ The taxonomy picker with suggestions uses this web service client-side. UPDATE: See the ...


6

I have tried implementing what you want to and it is working for me. Here are the steps I followed: 1) Create New Site Collection http://spurl/sites/test 2) Create Sub Site under that http://spurl/sites/test/sub 3) In the Term Store, created a a new TermGroup, TermSet and Term under it in the following order: 4) Also seen in the image, I assigned the ...


6

I had a similar issue this morning, with an external dataset with around 100,000 records. The way I worked around it was to create a SQL stored procedure to do the Read List operation, rather than querying the data directly. The Read Item operation can still be linked directly to the list, rather than requiring a second stored procedure. On the Read List ...


5

I had the same problem today when copying. Difference for me I was copying from one column to another. Both columns were managed metadata columns pointing to the same managed metadata. The reason I kept getting the error was because the column I read in was a Managed Metadata that allowed multiple values, the second column didn't. Therefore Specified ...


5

When setting the value of Taxonomy Fields always use TaxonomyField.SetFieldValue var sourceValue = sourceItem["SColumn"] as TaxonomyFieldValueCollection; var targetField = targetList.Fields["TColumn"] as TaxonomyField; targetField.SetFieldValue(targetItem, sourceValue); targetItem.Update(); Just setting targetItem["field"] doesn't update the hidden ...


5

In SharePoint 2013 it is not possible to build a security trimmed managed metadata navigation. I hope this feature will coming soon with a Cumulative Update or Service Pack. I am the owner of the german blog wich was mentioned here. I think i will provide my article in english too. Sorry for that!!


5

You can set a MultiValue Managed Metadata field by creating a TaxonomyFieldValueCollection and add this collection to the field by using the SetFieldValue method. First get the managed metadata field A possible way ( there are more ways ) to do this is to get the field by id $field = $item.Fields | ? {$_.Id -eq $fieldId} $tf = [Microsoft.SharePoint....


5

The logic is contained in VariationRoot.aspx which by default redirects users according to language and cookie settings by means of a custom control in the page layout (VariationRootPageLayout.aspx). You have a number of options for customising this logic if required, including replacing the custom control or adding some client-side logic using JavaScript, ...


5

I resolved the issue by setting the keywords in the following way: Microsoft.SharePoint.Client.Field entKeywordField = list.Fields.GetByInternalNameOrTitle("Enterprise Keywords"); TaxonomyField entKeywordFieldTaxonomy = ctx.CastTo<TaxonomyField>(entKeywordField); entKeywordFieldTaxonomy.SetFieldValueByValueCollection(item, new ...


5

Document management by metadata is the correct approach. I’ve worked both with Document Sets and without them. Document Sets have the benefit of storing documents that share one or more properties. They come in handy if you use a document library for storing multiple documents in an isolated environment. An example can be the use of marketing surveys records ...


5

If you're dealing with that many objects, I would create the term store and use the managed metadata fields. The reason is that once you get past more than 10 items, the lookup field gets a little unwieldy for anyone that uses it. If you use a managed metadata field, you can organize those values within your taxonomy and have a little more structure to the ...


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