SharePoint24x7 It's all about SharePoint.

20Jan/150

Article – Tiles (Metro UI) Navigation Web Part in SharePoint 2013

Posted by Joy

Modern UI (formerly knows as Metro-style UI) was introduced with Windows 8 operating system.

I was looking at providing the same navigation for a SharePoint site and then I found out that SharePoint 2013 Team Site template already provides a feature for the same. I’m sure lot of people are not aware of this and decided to blog about it.

Following is the out-of-the-box Tiles web part we will get when we create a new site using Team Site template:

Team Site Tiles web part

This Tiles web part was introduced in SharePoint 2013 using a new list template named “Promoted Links”. Let’s make use of this new list template and create a new Tiles based navigation web part.

Task 1 – Activating the required Feature

The “Promoted Links” list templates comes with a Features called “Team Collaboration Lists”. If you are using a site created from a Team Site template, most like this Feature is already activated. In case if you don’t see this list template and if you are using a site created from other than Team Site template, perform the following steps to activate the Feature:

  • Click Settings –> Site settings
  • Select Manage site features from Site Actions section
  • Activate the Feature “Team Collaboration Lists

Team Collabotation Lists Feature

Task 2 – Create a list using Promoted Links list template
  • Click Settings –> Add an app

Site settings

  • Select Promoted Links list template

Promoted Links list template

  • Give a name and click Create. I provided “Menu” as the name of the list.
  • Click the newly created list (in my example “Menu”)
  • Click “All Promoted Links” to go to All Promoted Links view

Promoted Links list

  • Click new item to add new items to be appeared in the Tiles web part. You need to enter Title, Background Image Location, Description, Link Location and also Launch Behavior. I uploaded few images to Site Assets library beforehand and specified their location for the Background Image Location.

New promoted link item

  • I entered 04 items to the Menu list I created
Task 3 – Add Promoted Links list view web part (Tiled view) into the page
  • Navigate to the page where you want to add the Tiles web part
  • Click Edit and go to edit mode
  • Click Insert –> Web Part and select the list from the Apps category

Add web part

  • Click Add and Save the page
  • Now you can enjoy the new Modern UI (Metro Style) Tiles web part

New Tiles web part

30Dec/140

Tips n Tricks – Navigating through SharePoint ULS logs using PowerShell

Posted by Joy

When troubleshooting SharePoint farms, ULS logs play a vital role. ULS logs are the entry point for both Administrator and Developers when they start investigating an issue in a SharePoint farm.

Usually ULS logs are created in the following directory in SharePoint servers:

C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS

ULS log files are easier to locate among other log files since their file name start with the server name and followed by a the timestamp.

ULS Logs directory

ULS logs contains very detailed information compared to Windows Event Logs. Following is a sample of a ULS log file:

ULS Logs

One of the big challenges/ pain point with regard to ULS logs are reading/ navigating through them. Since they are very detailed, going through them is really challenging. When we open a ULS log file, by default it opens in Notepad and it is really difficult to navigate through them.

Most of us try using lot of 3rd party tools for navigating through ULS logs without knowing that PowerShell also provide a powerful option for us to navigate through ULS logs.

Open SharePoint 2013 Management Shell and issue the following PowerShell command:

Get-SPLogEvent | Out-GridView

PowerShell command

This command will open up a new windows with a Grid View view of ULS log file. This allows us to navigate and filter ULS log entries easily compared to Notepad.

ULS Log Grid View

ULS Log Grid View Filtering

18Nov/140

Article – Customizing SharePoint 2013 Search Results with Query Rules – User Intent

Posted by Joy

One of the best new features of SharePoint 2013 Search is the introduction of Query Rules. Query Rules in SharePoint 2013 replaces the Best Bet functionality in SharePoint 2010.

Query Rules allows us to create:

  • Result Blocks
  • Promoted Results
  • Change Ranked Results
  • Act on user “Intent”
  • Publishing

Act on user “Intent”

Act on user intent is all about searching in a natural way. It means mixing our natural vocabulary with search queries.

Most of us refer to PowerPoint presentations as “Deck” and Word documents as “Doc”. In SharePoint 2010 search, when we want to search for any Word or PowerPoint content, you need to first search by giving the search query and then refine using file type.

What if we want to combine our natural vocabulary with search keywords? For example, what if I issue search queries such as “SharePoint deck” and “SharePoint doc” trying to locate Word or PowerPoint content which contains SharePoint keyword? In SharePoint 2010 search, it will search for content which contains “SharePoint deck” and “SharePoint doc” within the content. It doesn’t understand that “deck” and “doc” are two words we use in our day-to-day vocabulary. But in SharePoint 2013, if you search by giving “SharePoint deck” and “SharePoint doc”, it will return Word and PowerPoint content which contains “SharePoint” keyword within the content. SharePoint 2013 understands that “deck” and “doc” are two words which we use commonly in our day-to-day work.

Following is a screen capture of a search result without using any user intent:

SharePoint 2013 Search result

Following is a screen capture of a search result with the use of new SharePoint 2013 Search user intent features:

SharePoint 2013 Search result with user intent

SharePoint 2013 Search result with user intent

“Deck” and “doc” are two built-in user intents provided by SharePoint 2013 Search. We also can introduce custom user intent with the help of new Query Rules concept.

Adding custom user intents

We often refer images as “pics”. It will be very convenient for end-users for being able to search for images by combining “pics” user intent rather than searching and then refining using file type search refinement.

Following is a screen capture of a search result which gives no results when you use “pics” user intent since “pics” is not a built-in search user intent rule and it’s trying to search for content which contains “sharePoint pics” within the content:

SharePoint 2013 Search result

Following steps demonstrate how we can get custom user intents integrated to SharePoint 2013 search.

Task – Creating a custom User Intent Query Rule
  • Navigate to your Search Center. In my case, it’s http://intranet.team.com/search
  • Click Settings from top-right corner and select Site Settings to navigate to Site Settings page.
  • Select Search Query Rules from the Site Collection Administration section to navigate to Manage Query Rules pageSite Settings
  • Select Local SharePoint Results (System) for For what context do you want to configure rules? parameter and click New Query Rule to open Add Query Rule page.Manage Query Rules page
  • Give a Rule Name, and select Query Contains Action Term for Query Condition. Enter “pics” for the option Action term is one of these phrasesAdd Query Rule page
  • Select Add Result Block under Result Blocks in Actions section to open Add Result Block dialog boxAdd Query Rule page
  • Amend the Block Title and click Launch Query Builder to open Build Your Query window.Add Result Block
  • Select Pictures (System) for Select a query option and click Test query button and observe the SEARCH RESULT PREVIEWBuild Your QueryBuild Your Query
  • Click OK to go back to Add Result Block dialog. Change the Items value depending on how many items you need to show in the search result.Add Result Block
  • Click Settings link to expand Settings section. Select Picture Item for Item Display Template and click OK.Add Result Block
  • Click Save to exit from Add Query Rule page
Task 2 – Testing the custom User Intent Query Rule
  • Navigate to Search Center.
  • Search using the new User Intent. Following screen capture shows a result of a search query which is combined with “pics” user intent
    SharePoint 2013 Search result with user intent
1Oct/141

Article – Customizing SharePoint 2013 Results using Result Sources

Posted by Joy

SharePoint 2013 gives us a very powerful Search platform by integrating the power of FAST Search platform. One of the very useful capabilities of SharePoint Search is the ability to customize to suite to your requirement.

SharePoint 2013 Search allows not only to customize the Content Processing Pipeline but also to customize how search results are queried and displayed in the search result.

In SharePoint 2010 one of the many ways we could customize search result was customizing Search Scopes. A search scope in SharePoint 2010 defines a subset of information in the search index. Users can select a search scope when performing a search to restrict search results to the subset of information that they want. Generally, search scopes consists of specific topics and different content sources that are important and common to users in the organization. Following is a screen capture of how SharePoint 2010 configures it’s default search scopes.

SharePoint 2010 search scopes

In SharePoint 2013 terminology, we don’t have Search Scopes concept anymore and we have Result Sources as a replacement for search scopes. Result source in SharePoint Server 2013 is used to specify a provider to get search results from, and optionally to narrow a search to a subset of those results. Result sources are more powerful than search scopes which we used in SharePoint 2010. Following are the default result sources we get in as part of the default configuration of SharePoint 2013.

SharePoint 2013 Result Sources

SharePoint 2013 default result sources provides:

  • Everything – Local SharePoint results
  • People – Local People results
  • Conversations – Local conversation results
  • Videos – Local Video results

In this article lets explore how we can use Result Sources to customize the search results presentation to provide more user-centric search experience.

Scenario

When users navigate to out-of-the-box Search Center in SharePoint 2013 and execute a search result, it displays all the items which contains/ match the search keyword. Following is an example of a default search result which shows everything including Sites, Pages, Documents, tasks, Calendar items which match with the search criteria.

SharePoint 2013 built-in search result page

What we want to do is, to customize the default search result presentation to meet the following conditions:

  • Search result will display only the content authored by the user who is executing the search query.
  • Search result will display only the Word Documents and will eliminate Sites, Pages, Calendar items and Tasks even if there are matching items.

Solution

We will be customizing SharePoint Search Result Sources to provide the above custom search result presentation experience.

Task 1 – Creating a custom Result Source

  • Navigate to your Search Center. In my case I have a Search Center defined in the URL: http://intranet.team.com/search/
  • Select Settings and Site Settings to navigate to Site Settings pageSite Actions menu
  • Select Search Result Sources from the Site Collection Administration section to navigate to Manage Result Sources pageSite Collection Administration
  • Manage Result Sources page shows all the built-in Result Sources. Click New Result Source to add a custom Result Source.Manage Result Sources
  • Enter a Name for your custom Result Source. Leave Protocol as Local SharePoint. Leave Type and SharePoint Search Result. Click Launch Query Builder button to launch the Build Your Query window.Build Your Query
  • We will be using BASICS tab to build our custom search query. Set Property filter as shown below and click Add property filter button to add it to Query text area. Click Test query button to test the query and observe the SEARCH RESULT PREVIEW.Build Your Query
  • Set Property filter again with the following parameters as shown below and click Add property filter button to add it to Query text area. Click Test query button again to test the query and observe the SEARCH RESULT PREVIEW. Now you can see the effect of our custom search query and how it reduces the result displayed to end-user.Build Your Query
  • Click Save to navigate back to Manage Result Sources page

 

Task 2 – Associating the new Result Source with the Search Center

  • Navigate to your Search Center. In my case I have a Search Center defined in the URL: http://intranet.team.com/search/
  • Select Settings and click Add a page option. Enter a name for the page and click Create.Add a page
  • New page will be in edit mode and you can customize the web parts available in the new page.
  • Edit Search Results web part to associate our new Result Source.Edit Search Result web part
  • Select Change query button and select the newly created custom Result Source from the Select a query drop down and click OK.Edit Search Result web part

    Change Search query

  • Click OK from from the edit web part property page to exit edit web part property page.
  • Click Check it in and Continue to check in the new page
  • Click Publish it to publish the new page.

 

Task 3 – Adding the new page as a search vertical

  • Select Settings and Site Settings to navigate to Site Settings page
  • Select Search Settings from Search section
  • Locate Configure Search Navigation section in Search Settings page. Click Add Link … to add a new navigation link.Add a search navigation link
  • Enter a title for the Title: field. For the URL: field, browse for the the newly created page by using Browse… button. Click OK.Add a search navigation link
  • Click OK to exit Search Settings page

 

Task 4 – Test the new Result Source

  • Navigate to Search Center and perform a search. You will see the new result source being added to search result page.SharePoint 2013 search result with the new result source
  • Select the new result source and see how it applied the conditions we specified to show content authored by the user who is running the search query and to include only Word documents.New result source search result presentation
2Sep/140

Tips n Tricks – Enabling Geolocation field in SharePoint 2013

Posted by Joy

SharePoint 2013 introduced a new site column with a new data type called Geolocation which enables us to store Latitude and Longitude information. This enables us to use Bing Maps API and visualize information in a map within SharePoint.

When I started looking at using this new geolocation site column all sources directed me to standard exercise of adding a site column into a list using list settings page.

It turns out to be really frustrating that I couldn’t see any geolocation site column to add.

Add site column

Finally I found a PowerShell commandlet which adds a geolocation to a list and I managed to add a geolocation to my list. Following PowerShell commandlets adds a geolocation site column to a list:

$web = Get-SPWeb "http://intranet.team.com"

$list = $web.Lists["Contacts"]

$list.Fields.AddFieldAsXml("<Field Type='Geolocation' DisplayName='Location'/>", $true, [Microsoft.SharePoint.SPAddFieldOptions]::AddFieldToDefaultView)

19Aug/140

Article – What’s new and improved in Visio 2013 Workflow designer

Posted by Joy

Wave 14 of SharePoint and Office introduced a new capability into Visio – being able to design SharePoint workflows. Visio 2010 Premium edition was introduced with this capability and it helped Business Analysts to capture workflow process requirements easily and draw then within Visio and import them to SharePoint Designer to add the logic.

Visio 2013 introduces few new features and improvements with regard to designing SharePoint workflows and they are:

  • Modifying shape properties – in Visio 2010, we could only connect shapes with each other and change the shape description. In Visio 2013 we can change shape properties to properly describe what each shape does within the workflow.
    Capture2 
  • Stages – just like Steps feature which was introduced in SharePoint Designer 2010 for developing workflows, Stages help grouping activities together. Apart from grouping, Stages also provide the capability to control the flow of the workflow by specifying which stage to follow after finishing the current stage. We can use “if” conditions to control the movements between stages.Stages in Visio 2013
  • No more “vwi” files – in Visio 2010, after designing the workflow, we need to save the drawing into a special file type called “vwi” – Visio Workflow Interchange in order to import it to SharePoint Designer. In Visio 2013, you don’t have to save to any special file types and you can rely on the native “vsdx” file type and still import it to SharePoint Designer.
25Jul/141

Article – Enabling Continuous Crawling in SharePoint 2013 Search

Posted by Joy

Crawling is the mechanism which SharePoint Search uses to go through all the items in a given content source and build an Index. All the search queries get executed against the Index to provide the search result. Outcome of the search always depends on the freshness of the Index. In other words, if the Index is very fresh/ recent, we have the ability of pulling fresh/ recent content as part of the search query. If the Index is very old/ outdated, search result will contain outdated search results.

SharePoint used to provide 02 mechanisms to crawl content from a content source – Full crawl and Incremental crawl.

  • Full crawl – this forces SharePoint to go through the entire content source, no matter what is the status of the Index and traverse through all the items from the first item through the last item and re-build the Index. This is what we do as the very first thing after we add a new content source. Time it takes to complete a full crawl is always depends on the volume of the content. If the volume is high, we don’t recommend running frequent full crawls.
  • Incremental crawl – this instructs SharePoint crawler to crawl only the modified content (added/ changed/ deleted) from the last full or incremental crawl. This takes less time to crawl since it doesn’t have to traverse through the entire content source and crawl the entire content source.

Most of the organizations, schedule incremental crawls depending on how frequent their content get updated. Incremental crawl starts at a particular time and repeats regularly at specified times.

SharePoint 2013 introduces an alternate option for incremental crawls – Continuous crawl.

  • Continuous crawl – this is a new option in SharePoint 2013 and it applies only to SharePoint Sites. Like incremental crawls, a continuous crawl crawls content that was added, changed, or deleted since the last crawl. Unlike incremental crawls, continuous crawl automatically starts at predefined time intervals. The default time interval is 15 minutes. This is the ideal option for crawling SharePoint content that is changing quickly/ frequently. With this, we can ensure freshness of Index and search result.
Configuring continuous crawl
  • Open SharePoint 2013 Central Administration web site
  • Select Manage service applications option from Application Management section
  • Select Search Service Application instance
  • Select Content Sources link under Search Administration links in left hand side
  • Select either New Content Source or your existing SharePoint content source
  • Select Enable Continuous Crawls for Crawl Schedules option and click OK.Crawl Schedules
17Jul/140

Article – Configuring PerformancePoint Services (PPS) in SharePoint 2013

Posted by Joy

What is PerformancePoint Services (PPS)?

As per TechNet:

PerformancePoint Services in SharePoint Server 2013 is a performance management service that you can use to monitor and analyze your business. By providing flexible, easy-to-use tools for building dashboards, scorecards, and key performance indicators (KPIs), PerformancePoint Services can help individuals across an organization make informed business decisions that align with companywide objectives and strategy.

PerformancePoint Services lets you create rich dashboards, aggregating content from multiple sources and displaying it in a web browser in an understandable and collaborative environment. The rich interactivity of the dashboards lets you to analyze the latest information and work with the data quickly and easily to identify key opportunities and trends. PerformancePoint Services and its authoring tool Dashboard Designer let you display key performance indicators (KPIs) and data visualizations in the form of scorecards, analytic reports, and filters. You can integrate with SQL Server Reporting Services (SSRS)and Excel Services in addition to create scorecards that bring together data from multiple data sources to track and monitor key drivers of your business.

Configuring PerformancePoint Services is very easy if you have experience already configuring services such as Excel Services, Secure Store Services, PowerPivot, etc…

In this article I’m trying to help you with the various information which are required for configuring PerformancePoint Services service application.

Prerequisites for configuring PPS:

  • SharePoint Server 2013 Enterprise – before we get started with the configuration of PPS, we need to make sure that we have SharePoint Server 2013 Enterprise edition in order to use PPS. PPS is available only with the Enterprise edition of SharePoint Server.
  • ADOMD.NET – SharePoint 2013 Prerequisites Installer installs ADOMD.NET 9.0 automatically in to your environment. However, PPS requires ADOMD.NET 10 and ADOMD.NET 11 to be installed in your environment.
Task 1 – Verify what version of ADOMD.NET is installed in your environment
  • Navigate to C:\Program Files\Microsoft.NET\ADOMD.NET\
  • If you have ADOMD.NET 9, ADOMD.NET 10 and ADOMD.NET 11 installed, you will see something similar to the followingADOMD.NET install folder
  • If you don’t have either 100 or 110 folders, which means you don’t have either ADOMD.NET 10 or ADOMD.NET 11 installed in your environment. Depending on the version you need to install, you can use either of the following links to download and install ADOMD.NET:
Task 2 – Grant Application Pool Service Account access to SharePoint Content Database
  • Open SharePoint 2013 Management Shell. Make sure to Run as Administrator.
  • Grant application pool service account access to the content database using following cmdlets
    $webApp = Get-SPWebApplication
    http://intranet.team.com

    $webApp.GrantAccessToProcessIdentity(“TEAM\SP_Services”)

Task 3 – Create PerformancePoint Service Application instance
  • Open SharePoint 2013 Central Administration web site
  • Navigate to Manage service applications page from Application Management section
  • Select New from the Create group in the ribbon and select PerformancePoint Service ApplicationNew service application
  • Enter a Name, Database Server, Database Name and Application Pool details and click Create.Capture2
  • Click OK in the service application instance creation conformation page
Task 4 – Start PerformancePoint Services service
  • Open SharePoint 2013 Central Administration web site
  • Navigate to Manage services on server from System Settings section
  • Check the status of the Performance Point Service service. Start it if it’s not started already.
    Capture4
9Jul/140

Article – Anonymous Crawl Configuration in SharePoint 2013

Posted by Joy

SharePoint 2013 introduces a new approach for passing credentials to Search Crawler for crawling public-facing sites with Anonymous authentication. SharePoint Search requires a user account for being able to crawl content. One of the bottlenecks we had to deal with SharePoint 2010 Search was difficulty of crawling public-facing sites with Anonymous authentication. SharePoint 2010 requires a user account for crawling content from sites, even if they are configured for Anonymous authentication. SharePoint 2013 resolves this issue by introducing a new approach – Anonymous which eliminate the need of passing an user account and trying to authenticate for crawling content for public-facing web sites with anonymous authentication.

Following are the ways we can configure SharePoint 2013 to pass credentials to SharePoint Search to crawl content:

  • Default Crawl Account
  • Specific Account
  • Client Certificate
  • Form credentials
  • Cookie
  • Anonymous

Following steps demonstrate how to configure SharePoint Crawler to use new Anonymous option to crawl public-facing web sites:

Task 1 – Configure public-facing web site Content Source

  • Open SharePoint 2013 Central Administration web site
  • Navigate to Manage service applications from Application Management group
  • Select Search Service Application instance and navigate to Search Administration page
  • Select Content Sources from the left hand side Search Administration linksSearch Administration links
  • Select New Content Source from Manage Content Sources page
  • Enter Name for the Content Source and select Web Sites option for Content Source Type.
  • Enter web site URL for the Start Address field and click OK.New Search Content Source

 

Task 2 – Create a Crawl Rule to use Anonymous option

  • Select Crawl Rules from the left hand side Search Administration links.Search Administration links
  • Select New Crawl Rule from the Manage Crawl Rules page
  • Enter Path and select Include all items in this path option from the Crawl Configuration section
  • Select Anonymous access option for the Specify Authentication sectionCrawl Rules

 

Task 3 – Crawl content

  • Select Content Sources from the left hand side Search Administration links
  • From the context menu for the new content source added, select Start Full Crawl to start crawling contentFull Crawl