Pages

Showing posts with label Managed Metadata. Show all posts
Showing posts with label Managed Metadata. Show all posts

Monday, November 18, 2013

SharePoint 2010 - Users cannot edit managed metadata columns

I was working on a SharePoint solution for one of our customers. I created a couple term sets and connected these to corresponding managed metadata site columns. After adding the site columns to a SharePoint list I wanted to change the name of the columns. This wasn't possible because I got the SharePoint access denied screen! Very strange because I had all the correct permissions to the term store group. After searching on Google I found out that I didn't had permissions to a hidden list! This is the TaxonomyHiddenList. You can find this list by adding the following behind your site URL:

/Lists/TaxonomyHiddenList/AllItems.aspx

Check out the permissions of the list to see if the inheritance is broken. This often happens when sites are created with a custom solution. This was at least the case at our customer.


Monday, August 26, 2013

SharePoint 2013 Managed Metadata navigation - End users cannot see the top navigation

For one of our customers I decided to use the Managed Metadata navigation feature. This is a really cool new feature in SharePoint 2013. I did encounter one issue reported by the administrators. Apparently the end users weren't able to see the top navigation. Strange! Let's take a look at an example I created to explain the problem.


The top navigation in this site is created by using a term set:



Every term can point to a location in SharePoint, for example a site:


I did this for all the sub terms: Subsite A and Subsite B. Apparently that's not sufficient! The main term also needs a location. After I added a location the problem was solved and the end users were able to see the top navigation.

Monday, March 12, 2012

SharePoint 2010 - Term store and permissions

Are you also wandering what the permission structure is surrounding the term store?

http://office.microsoft.com/en-us/sharepoint-server-help/manage-permissions-and-roles-for-term-sets-HA101631579.aspx

Wednesday, March 7, 2012

SharePoint 2010 - Page lay-out and Managed Metadata column

I was having issues with a new page lay-out and displaying a managed metadata column. The column got displayed like this:

CustomTag_0:TaxonomyFieldControl

This prevented my page to load correctly. I found this great article from Dave Perkinson:

http://underthehood.ironworks.com/2010/03/sharepoint-2010-how-tos-embedding-managed-metadata-page-fields-in-your-page-layouts.html

The problem is that your page layout is missing the requisite assembly reference to include the Taxonomy Picker control. You can fix this problem by adding the following reference to the top of your page layout:

<%@ Register Tagprefix="Taxonomy" Namespace="Microsoft.SharePoint.Taxonomy" Assembly="Microsoft.SharePoint.Taxonomy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>"

This worked like a charm! Thanks Dave :-)

I also found the following solution:
http://blog.degree.no/2011/01/sharepoint-2010-adding-taxonomyfieldcontrol-to-custom-page-layout/


<%@ Register Tagprefix="Taxonomy" Namespace="Microsoft.SharePoint.Taxonomy" Assembly="Microsoft.SharePoint.Taxonomy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
Then change the <CustomTag_0:TaxonomyFieldControl> to <Taxonomy:TaxonomyFieldControl> and off you go (remember there is a closing tag too, by the way..):
<Taxonomy:TaxonomyFieldControl FieldName="81d247d1-0373-4a2d-9e81-d4b69bf3e091" runat="server"></Taxonomy:TaxonomyFieldControl>

Tuesday, February 7, 2012

Office 365 - Enabling Managed Metadata

I just saw a great tweet on Twitter about activating managed metadata in Office 365:

http://www.sharepoint-tips.com/2012/02/enabling-managed-metadata-in-office365.html

Thanks to Ishai Sagi! :)

Tuesday, December 13, 2011

SharePoint 2010 - Error while trying to remove a managed metadata column

I wanted to remove a managed metadata column that was attached to a term store. I only kept getting the following error message:

ERROR: The column cannot be deleted because it is currently part of a composite column

I found this great post:

http://sharepointyankee.com/2011/10/17/error-the-column-cannot-be-deleted-because-it-is-currently-part-of-a-composite-column-index/

My solution was to remove all indexes. That worked for me :)

Thanks to Geoff Varosky :)

Wednesday, September 7, 2011

SharePoint 2010 - Creating a knowledge base part 2


In the first part of this series, click here, I talked about a knowledge centre created for one of our customers. In this article I will show you how easy it is to create a knowledge centre with out-of-the-box SharePoint functionalities.

Step 1 – Create the site
The first step is to create a new site based on the Enterprise Wiki template:


I really like the Wiki. It is easy for the users to create new pages, by using the Site Actions menu, or by adding [[ ]] to a word or sentence. Let’s say you created a new page about hiring new employees. This page needs to connect to another page about the bonus system for recruiting new employees. Only you are not the author for this page and want another user create the page. Just perform the following action:

Friday, September 2, 2011

SharePoint 2010 - Creating a knowledge base part 1

A couple of weeks ago I saw a tweet from Jennifer Mason (@jennifermason). She asked if someone is using metadata navigation in lists and libraries. This was a coincidence because during one of my recent projects a client asked us if we could implement an internal knowledge centre. This centre had to be used for storing internal procedures. This varied from internal trainings to what to do in a case of an emergency. The customer wanted to create the procedures, in SharePoint 2010, through using text, documents and pictures. The procedures had to be categorized per department. This immediately brought my attention to the enterprise wiki site template and managed metadata navigation.