Showing posts with label Managed metadata services. Show all posts
Showing posts with label Managed metadata services. Show all posts

Tuesday, May 31, 2016

Configuring the SharePoint 2013 Managed Metadata service for Navigation

Configuring the SharePoint 2013 Managed Metadata service for Navigation

One of the new features of SharePoint 2013 is the ability to save your custom navigation in the Managed Metadata Service Application. Some of my coworkers were playing with it and noticed it worked fine on farms set up with the Farm Configuration Wizard (Booooo!) but did not work on Farms where the service applications had been lovingly created by hand. With some help we were able to find the difference and fix it. I would tell you how now, but I’m building up for the big reveal at the end. Big reveals are the hallmark of great storytelling.
We found the problem when going to a site collection with the Publishing Feature enabled and going to Site Settings > Navigation. We tried to enable the Managed Navigation, which stores our custom navigation links in the Managed Metadata service. Here’s what the problem looked like:
Office-PC 8-8-2012 10.11.05 PM -2
We checked the two boxes to enable Managed Navigation. Since we were turning it on for the first time we didn’t have a term set created to store our navigation in. Clicking the “Create Term Set” button on the bottom resulted in the following error:
Failed to create term set. A default managed metadata service connection hasn’t been specified.
This message made it sound like the service application wasn’t created (it was) or that it wasn’t in this web application’s proxy group (it was), but that wasn’t the case. We discovered there’s a magic checkbox in the Proxy for the Managed Metadata Service application that makes it available for navigation. The Farm Configuration Wizard checks that checkbox. I hadn’t. Here’s how to do it. Go into Central Admin > Manage Service Applications and highlight the Managed Metadata Service Proxy. Then click Properties in the Ribbon.
Office-PC 8-8-2012 10.12.25 PM -2
In the Properties for the Proxy, check the box next to “This service application is the default storage location for column specific term sets.”
Office-PC 8-8-2012 10.12.56 PM
If you’d prefer to do it with PowerShell (and honestly why wouldn’t you?) you can do it like this:
Office-PC 8-9-2012 9.05.41 AM
and for your copying and pasting pleasure:
$saproxy = Get-SPServiceApplicationProxy | Where-Object { $_.typename -like "Managed*" }
$saproxy.Properties.IsDefaultSiteCollectionTaxonomy = $true
Regardless of how you change that setting, either through PowerShell or the wimpy way through Central Admin, you should be able to create a Term Set when enabling Managed Navigation. Victory looks something like this:
Office-PC 8-8-2012 10.23.24 PM -2
Hope this help,

Tuesday, May 5, 2015

How to Apply Metadata Navigation Filtering in SharePoint 2013

How to Apply Metadata Navigation Filtering in SharePoint 2013

In this post I will show how to set up Metadata Navigation Filtering in Share Point 2013. This is one of the most powerful features available in helping users quickly find what they need without writing any code, it really just needs to be turned on and configured.

I start on the Home Page of the Site which is at the top level site of the site collection created and configured in the previous posts. Metadata Navigation and Filtering is a Site Feature that has to be activated for this to work.
On the right side I click on the site Actions Gear and go to Site Settings where I will activate the Site Feature, Metadata Navigation and Filtering.


This site feature is not activated on the Team Site Template so I click Activate.

When I see the blue icon that says Active, I know I’m good to go.
I click the link in the Quick Launch bar to get to the gdpByStateReports Library I configured in previous posts.

I click the Library Tab.

I click the Library Settings Icon.

We are going to use th Metadata navigation settings that is now available on the Library to pivot on these two Metadata columns.
This will allow users to find reports immediately based on Metadata regardless of which older they are in.
I click the Metadata navigation settings link. This link was not available on the Library Settings page until the Metadata Navigation and Filtering Site Feature was activated.

This is the Metadata navigation settings page.
Here we see two main areas: Configure Navigation Hierarchies and Configure Key Filters. These two work hand-in-hand to basically give users multiple levels of filtering in an amazing UI that gets added just below the Quick Launch Bar. (I highlighted some areas of particular importance).
The Navigation Hierarchies and only use: Content Type, Single-value Choice fields, or Managed Metadata Fields and the Key Filters can only use Content Type, Choice Field, Managed Metadata Field, Person or Group Field, Date and Time Field, or Number Field. Between the two if you do some planning with this in mind you can create very powerful User Interfaces out of the box.
We are going to use the StateOfOrigin and YearOfReport choice fields in Both areas and we are going to leave the Folders in the Navigation Hierarchy Fields.
To configure the controls, you select the columns on the left side and click the Add button which moves them over to the right side. When you are done your page should look like the figure above. When it’s ready you can click OK at the bottom of the page. Clicking OK Not Shown.
Now that its all configured we can click the gdpByStateReports link in the breadcrumb where we will see our amazing U.I.

Just below the Quick Launch, Share Point has added the Navigation Hierarchy and Key Filter Controls. I will start by clicking the State Of Origin in the top control.

This expands to show the available fields (the options in choice column) I click on AR (Arkansas)
Immediately the content area of the web page shows all the reports that have the value AR in the StateOfOrigin column, REGARDLESS of which folder they reside in!
With the state of Arkansas Selected in the Hierarchy control (AR) I go to the key Filters click the drop down menu for YearOfReport, You may have noticed that the StateOfOrigin Drop down disappeared because I already filtered on that column.
I select 2010 and click Apply. My results are immediately apparent. I now see all reports for the State of Arkansas from the year 2010, regardless of which Folder the result set resides in.
If I click the link to go back to the Document Library I can see that it resets my controls to their original state an returns the YearOfReport drop down to the U.I.
That’s it! Users can now quickly and efficiently parse through folders with out of the box functionality.

Friday, January 16, 2015

Managed Metadata Navigation not showing to users

Managed Metadata Navigation not showing to users

I created a Managed Metadata service and created group, term-set and terms
I gave full access to application pool service account. read access to all the users via AD Security Group.
I set up navigation to use Managed Navigation (Managed Metadata Service).
I am logged-in as farm admin and able to view the navigation when i browse site. But user are not seeing navigation.
One thing i noticed is when i give users full access or designer access to site they will be able to see the navigation. but i don't want to give all users full access or designer access to the site.
Solution :
Go to site settings => Term Store Management, then select the group recently created.
Go to the navigation tab and make sure your simple link or header is selected for the terms.

I hope this helps.

Tuesday, November 25, 2014

Migrate Managed Metadata Service to SharePoint 2013 error

Migrate Managed Metadata Service to SharePoint 2013 error

Managed Metadata Service connection i currently not availible
The Managed Metadata Service connection is currently not available. The Application Pool or Managed Metadata Web Service may not have been started. Please Contact your Administrator.
And in the ULS logs:
Failed to get term store for proxy ‘Managed Metadata Service Application Proxy’. Exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.     at Microsoft.SharePoint.Taxonomy.Internal.XmlDataReader.GetDateTime(String name)     at Microsoft.SharePoint.Taxonomy.Internal.SharedTermStore.Initialize(IDataReader dataReader, Guid termStoreIdValue, Boolean fromPersistedData)     at Microsoft.SharePoint.Taxonomy.Internal.SharedTermStore..ctor(IDataReader dataReader, Guid termStoreId, Boolean fromPersistedData)     at Microsoft.SharePoint.Taxonomy.Internal.DataAccessManager.GetTermStoreData(MetadataWebServiceApplicationProxy sharedServiceProxy, Boolean& partitionCreated) b195739c-8011-5023-8da3-f7cd968a5d80
The steps I did to get the error above:
  • Restore Managed Metadata Service database in the new SharePoint 2013 environment using SQL Server Management Studio
  • Used powershell to create new Managed Metadata Service application: (where -DatebaseName ‘Managed Metadata Service’ is my restored database.)
    New-SPServiceApplicationPool -Name 'ManagedMetadataServiceApplicationWebAppPool' -Account 'SP2013Services'
    $applicationPool = Get-SPServiceApplicationPool -Identity 'ManagedMetadataServiceApplicationWebAppPool'
    $mms = New-SPMetadataServiceApplication -Name 'Temp Managed Metadata Service Application' -ApplicationPool $applicationPool -DatabaseName 'Managed Metadata Service'
    New-SPMetadataServiceApplicationProxy -Name 'Managed Metadata Service Application Proxy' -ServiceApplication $mms -DefaultProxyGroup
  • Open Central Administration -> Application Management -> Manage Service Applications -> Manage Metadata Service Application -> Error!
The solution
  • Make sure you have started Managed Metadata Web Service in Central Administration -> System Settings -> Manage services on server
  • Make sure the account you used in the script above and that the farm account have appropiate rights on database intended for migration (default db owner)
  • Detach database in SQL Server Management Studio
  • Using Central Administration, remove the Managed Metadata Service Application (and associated data – do not forget to detach database before or it will be removed!)
  • Re-create Manage Metadata Service Application with a new database:
    $applicationPool = Get-SPServiceApplicationPool -Identity 'ManagedMetadataServiceApplicationWebAppPool'
    $mms = New-SPMetadataServiceApplication -Name 'Temp Managed Metadata Service Application' -ApplicationPool $applicationPool -DatabaseName 'New Managed Metadata Service'
    New-SPMetadataServiceApplicationProxy -Name 'Managed Metadata Service Application Proxy' -ServiceApplication $mms -DefaultProxyGroup
  • Verfiy that the term store management tool page is now working
  • Change database of the Managed Metadata Service application to your database intended for migration:
    Set-SPMetadataServiceApplication -Identity $mms -DatabaseName 'Managed Metadata Service'
  • Run iisreset
  • Verfiy that the term store management tool page is now working and that you can see terms from your old environment

Optimising bulk inserts with Entity Framework 6

Optimising bulk inserts with Entity Framework 6 In Entity Framework 6+ the database context implements the  unit of work  pattern so th...