New answers tagged managed-metadata
0
I had almost the same requirements and come to creation of web part that interacts with Managed Metadata (to get terms from the specified term set) and Search (to get results). Then it builds a tag cloud for top results. Please check the link for more details.
0
It took me a bit of discovery, but I figured out that there are some values you can actually edit for NavigationLinkType.FriendlyUrl. Microsoft doesn't have any documentation that shows how you can edit them. Below is an example that will show better than I can explain:
NavigationTerm term = navigationTermSet.CreateTerm("Communities", ...
0
In central admin, did you check to make sure your managed metadataservice is attached to your web application? Go to central admin /_admin/WebApplicationList.aspx. select the web application and click the "Service connections" in the ribbon. make sure you meta data service is "checked".
If it is, then go to the actual metadata service and check to see ...
1
There is a lot to think about when provisioning a taxonomy field.
For example. You need to make sure TaxonomyFieldAdded feature is activated (as you do)
But also you need to provision a field of type Note that is bound to your taxonomy field.
And lastly, you need to connect your field to a TermSet to be able to use it.
This link is of great help to me ...
0
Why are you setting every employee as a managed metadata item?
It would be a better way to make a list where you add every employee in than add your metadata column company to every emoployee this way you can filter the list of employees on your metadata column country.
0
I tried all of the above with no success, but managed to bring my MM term store back online with a stop and start of ALL running instances of the Managed Metadata Web Service from the Services on Server page
0
I think you can make a call like this to get the values for owstaxidmetadataalltagsinfo refiner:
http:// siteurl /_api/search/query?querytext='*'&refiners='owstaxidmetadataalltagsinfo'
You will get some values with this format:
L0|#036f7c08a-0176-47e9-9d70-070291ce0e32|Data Warehousing
2
In this case I would recommend you to add the new department names to the manage metadata store and merge the old departments with the new values. You shoul check out the following blog post http://term-management.com/2012/10/11/merging-terms-in-the-sharepoint-2010-term-store-2/
0
This is the url, you already posted it.
http://server/_api/search/query?querytext='Query text'&refiners='property1,property2,etc'
If this doesn't work then your managed property is either not crawled, you have no access with that user, you have the refiner name wrong or simply there are no results.
0
Did you added site column as a Taxonomy field yet if not then follow this blogpost,
Creating a site column that holds a value from managed meta data term
store is not directly available.
We first need to create a site field which is of type taxonomy and
then we need to create one feature which is scoped at site level and
in feature activation ...
0
Based on my knowledge you could do that in someway.
I found a post of Mastykarz where I explain how get the list of terms by js. Using this you should be able to do a search query: http://blog.mastykarz.nl/building-global-navigation-sharepoint-2013/
Another good point of view is this tool: http://sp2013searchtool.codeplex.com/
it could help you to ...
2
You can use PowerShell to create a Crawled property and a managed property.
You can use the following code to create and map the properties
Param(
[string]$crawledProp,
[string]$managedProp,
[int] $typeManagedProp
)
# TypemanagedProp 1 = Text 2 = Integer 3 = Decimal 4 = DateTime 5 = YesNo 6 = Binary 7 = Double
$snapin = ...
0
You probably have the wrong crawled property mapped. In my case the site column was named Loan Type and that created the following 4 crawled properties
Loan Type
Loan_x0020_Type
ows_Loan_x0020_Type
ows_taxId_Loan_x0020_Type
I selected ows_Loan_x0020_Type and did a full crawl and it worked.
0
Here is the post explaing the issue, http://sureshpydi.blogspot.in/2013/04/there-are-no-addresses-available-for.html
0
I have found a workaround for this issue.
If you create a new template and set the desired "local" default value on the Doc Property for that template, you can set the content type to use the "local" template under Advanced Settings for the content type.
This definitely works, but I am still interested in a more elegant solution.
Top 50 recent answers are included
