Posts

Showing posts from 2015

SharePoint Server 2013 and SQL Server Full-Text Search

Image
There's long been some debate as to whether or not SharePoint requires you to install the SQL Server Full-Text Search feature on the database server. I've worked on the premise that it doesn't - SharePoint has its own search engine, etc.

However, the Access Services service application DOES require the Full-Text Search feature. If this feature is not installed, you'll get an error when you attempt to provision an Access Services service application that states "The Application Database Server does not have the Full-Text Search feature installed".

























Access Services actually places a whole bunch of extra demands on the database server in addition to the Full-Text Search requirement. For example:

The database server must be running at least SQL Server 2012 (SharePoint Server 2013 will run happily on SQL Server 2008 R2 SP1)The SQL Server instance must support mixed mode authentication.The SQL Server instance must support Named Pipes in addition to TCP/IP. For more i…

Programming eDiscovery in SharePoint Server 2013

Recently I needed to get a grip on how to work with the eDiscovery tools in SharePoint 2013 from the server-side object model. There's not much information out there on how to do this (and some of the information out there is plain wrong), so I built a proof-of-concept console app to work through the key features, including:

Programmatically retrieving an eDiscovery case.Creating a new source.Creating a custodian.Creating a new source.Creating a new eDiscovery set.Using queries and exports.Applying in-place holds to eDiscovery sets.
I'll keep the explanation to a minimum, as I'm hoping the code largely speaks for itself. I'll assume you know the basic concepts of eDiscovery in SharePoint 2013, including how to work with cases, sources, sets, queries, and exports through the UI. To use the code, you'll need assembly references to Microsoft.SharePoint.dll and Microsoft.Office.Policy.dll. All the eDiscovery classes you need are in the Microsoft.Office.Server.Discovery

Custom Workflow Activity for Setting Managed Metadata Field Values

Image
In this post I'll show you how to build a custom workflow activity in Visual Studio that can update managed metadata field values in a SharePoint 2013 list or library. This is the final part of a three-part series on working with managed metadata fields in workflows:
Getting and Setting Managed Metadata Fields in SharePoint 2013 Workflows. In this post, I introduce the scenario, explain why you can't use built-in list actions to work with managed metadata fields, and provide a conceptual overview of the custom workflow activities approach.Custom Workflow Activity for Getting Managed Metadata Field Values. In this post, I'll walk you through how to build a custom workflow activity in Visual Studio that gets managed metadata field values from a list item.Custom Workflow Activity for Setting Managed Metadata Field Values (this post). In this post, I'll walk you through how to build a workflow activity that sets managed metadata field values on a list item. I've said it…

Custom Workflow Activity for Getting Managed Metadata Field Values

Image
In this post I'll show you how to build a custom workflow activity in Visual Studio that gets managed metadata field values from a SharePoint 2013 list or library. You can use the workflow activity in any SharePoint Designer list workflows, including on Office 365 sites - custom workflow activities in SharePoint 2013 are entirely declarative, so deploying to SharePoint Online is not a problem.

This is the second of a three-part series on working with managed metadata fields in workflows:
Getting and Setting Managed Metadata Fields in SharePoint 2013 Workflows. In this post, I'll explain the concepts behind my approach and explain why you can't use built-in list actions to work with managed metadata fields.Custom Workflow Activity for Getting Managed Metadata Field Values (this post). In this post, I'll walk you through how to build a custom workflow activity in Visual Studio that gets managed metadata field values from a list item.Custom Workflow Activity for Setting Ma…

Getting and Setting Managed Metadata Fields in SharePoint 2013 Workflows

In many workflow scenarios, you'll want to get a field value from a list item in one list and apply that value to a list item on another list. With most field types, you can do this easily using workflow variables and built-in list actions in SharePoint Designer 2013. However, it's widely acknowledged that working with managed metadata fields in SharePoint workflows is a bit of a nightmare. To get around the problem, I built some custom workflow activities to get and set managed metadata fields in SharePoint Designer workflows.

This is the first of a three-part series on working with managed metadata fields in workflows:

Getting and Setting Managed Metadata Fields in SharePoint 2013 Workflows (this post). In this post, I explain why you can't use built-in list actions to work with managed metadata fields, and walk through how to approach the problem.Custom Workflow Activity for Getting Managed Metadata Field Values. In this post, I'll walk you through how to build a cus…