Showing posts with label SharePoint 2013. Show all posts
Showing posts with label SharePoint 2013. Show all posts

Sunday, 31 March 2013

New JavaScript Display Template in SharePoint 2013

No comments:
Excellent Post at about the new JavaScript Display Template in SharePoint 2013.

JavaScript Display Template Content Type - This is a new Content Type Introduced in SharePoint 2013 to Create a new custom CSR JavaScript Display Template in the Master Page gallery of the site. JavaScript Display Template Content Type has some special Site Columns added to it that will help specify the target element (view,webpart etc..) where the JavaScript File’s magic or custom rendering will be Implemented.

Lets Look at the Steps to upload a new Js file as a new Javascript Display Template and look at the description of Site Columns.

1. Navigate to the Master Page Gallery (Site Settings -> under Web Designer Galleries -> Master Pages).

2. Select Files tab and then Upload Document.

3. Browse to the new JavaScript file that you have created and select Ok.

Task Status Indicators
JavaScript Display Template Upload Js
4. Next select “JavaScript Display Template” in the Content Type drop-down.

Add Javascript display template SharePoint 2013
5. Next specify the Name, Title, Description properties along with some special properties like “Target Control Type Standalone,Target Scope and Target List Template ID” for this new JS file.

Target Control Type - By description “Target Control Type is the Type of Control that you will be using in this Display Template or JavaScript File”. For example if your Display Template or JavaScript File will be controlling the rendering of a View in a List, then the Target Control Type value should be “View”.
There are three possible options

  • Form
  • View
  • Field

Standalone - Specifies if you need to include this JavaScript File Override during view selection.Default options are

  • Override
  • Standalone

Target Scope - URL of the website this override applies to. This can be a relative path to your Site Collection or subsite.

Target List Template ID - Specify the ID of the list Template type this Override or JavaScript render applies to.Use the list Here to determine the Template Id for the type of list that you will applying this rendering upon.
For example, 107 would be the Target List Template ID for a Tasks List.

Upload Js template SharePoint 2013

Upload JS Template SharePoint 2013

Once your done adding document properties Save it.

Don’t forget to Publish it as major Version before start using it.

Saturday, 30 March 2013

List of the Snippets for Master Pages in SharePoint 2013

No comments:
In SharePoint 2013 the new Snippet Gallery provides an easy way to get Codes for very useful SharePoint Out-of-box Controls like Navigation,Security Trimming Control,Edit Panel Control,Search,Device Channel and more.

For a typical Master Page you can add Snippets for the following -
"Master Page Snippets SharePoint 2013"

Navigation - The navigation snippets provide common navigation links and menu items on a site page.
  • Top Navigation : The navigation snippets provide Top Navigation links.
  • Vertical Navigation : The navigation snippets provide Left Navigation links
  • Search Box: Place the search box component on your page to allow users to search your site
Administration –
  • Site Title : This is a ‘Site Title’ Control which users with administrative permissions can change in Site Settings.
  • Site Logo : This is a ‘Site logo’ Control which users with administrative permissions can change in Site Settings.
  • Sign In : Only authenticated users can see the ribbon. To give anonymous users a way to log into your site, insert the sign in snippet, which authenticated users won’t see.
Containers –
  • Edit Mode Panel :To display content, including snippets, to contributing site authors only, place it inside an Edit Mode Panel. (For example, an Edit Mode Panel might contain instructions and notes for page authors.)
    • Show Only in Edit Mode
    • Show Only in Regular Mode
  • Security Trim :To display content only to those users who have a specified level of security permissions, you can use a Security Trim Control.
    •         Show to Authors
    •         Show to Authenticated Users
    •         Show to Administrators
  • Device Channel Panel : A Device Channel Panel displays the content defined within it to one or more specified Device Channels. Device Channel Panels are typically used on Page Layouts to selectively hide certain regions and functionality from or show them to specified channels, and define channel-specific CSS.
Web Parts  -
Media and Content –
  • Media Web Part
  • Content Editor
  • Get started
  • Image Viewer
  • Page Viewer
  • Picture Library
  • Script Editor
  • Silverlight Web Part
"Media and Content"

Dynamic Content –
  • Content Query
  • Summary Links
  • Table of Contents
  • Timeline
  • Relevant Document
  • XML Viewer
  • Term Property
  • Rss Viewer
  • Sites in Category
  • Categories
"dynamic content"

 Other WebParts –

Other webparts snippets

Custom ASP.NET Markup -
If you have any ASP.NET elements you’d like to include that aren’t available in the Snippet Gallery, paste the markup for those elements into the text box below, click the Update button, and paste the resulting HTML Snippet into your page.

Change Master Page and Theme in SharePoint 2013

1 comment:
Changing a Theme and a Master Page can be done while Selecting and Trying out Themes using the
 the new "Change the Look" option in Site Settings or under Look and Feel in Settings menu.

Lets Look at the Steps -

Select the "Change the Look" in Settings Option.

Here you can find some really good SharePoint Themes which can switch the look of your Office 365 site in minutes. Here is a quick look of the Themes

When you select one of the themes you would find some Interesting Options like you can Change the background Image of the site,select a color Scheme, Select the desired font and a desired Master Page. Once you are done click on “Try it Out” on the top right of the Master Page.

Next click on “Yes, Keep it” to apply this new Look.

Here is the Final Result.

Sunday, 3 March 2013

Customize Top Suite bar in SharePoint 2013

No comments:
Here are some Importnat links that will be used to Customize Top Suite bar in SharePoint 2013.

To Customize left "SharePoint' or 'Office 365' text in top left see -

To Customize NewsFeed,Skydrive,Sites bar (DelatSuitelinks) see -

To Customize Shared,Follow,SYNC bar (Promoted Actions) see -

Error Creating Layout Page 'Sorry, something went wrong..' in SharePoint 2013

No comments:
Past day I tried to follow a new article Here on for Creating Custom Layout Pages in SharePoint 2013 but when I clicked on "Create a Layout" link in Deisgn Manager I got the following error -

The error has no proper explanation and I couldn't find anything on google as well.I tried Re-Creating Site and Re-enabling Publishing feature in the site but nothing worked.
Finally, Re-Creating the Site Collection worked and the regular popup started appering.

Sunday, 10 February 2013

Programmatically Create Social Profile in SharePoint 2013

No comments:
Its been a while since I wrote a blog entry. Here is something that will be useful to all.

In User Profiles each user now has a Social Profile to track interact with Social activities or properties of a User. In addition to the existing ones in SharePoint 2013 Ms has Included the following new objects that represent Users and User Properties:

The SocialActor object represents users (and other entities) for feed,following and other social activities.

The PersonProperties object contains general user properties and user profile properties. PersonProperties is the primary API for accessing user properties from client-side code.

//Create a Social Profile with SPSocialFollowingManager

SPSocialFollowingManager _followManager = new SPSocialFollowingManager(profile);

//Create a Social actor of type Document

SPSocialActorInfo newActor = new SPSocialActorInfo();

newActor.ActorType = SPSocialActorType.Document;

//Follow the document actor
newActor.ContentUri = new Uri('path of document to follow');

Please Note that to Create or Change user profiles, you must use the server object model. User profiles and user profile properties from client APIs are read-only (except the user profile picture).

Sunday, 18 November 2012

SharePoint 2013 Use Project Sites to Manage Work

No comments:
SharePoint 2013 Use Project Sites to Manage Work

Project sites enable people in an organization to effectively collaborate on lightweight projects. Project managers can quickly get a sense of what’s going on in a project, and team members can quickly see how their work fits into the overall context. Project sites also enable teams to access and share relevant data, documents, and communication.

A project site provides the following:
  • Project Summary Web Part.
  • Visual timeline of the project’s tasks.
  • Project task schedule.
  • Library for storing relevant project documents.
  • Notebook for quickly capturing and organizing information about the project.
  • Shared calendar for team events.
  • Ability to connect to the Project Server 2013 client application.
When SharePoint is connected to Exchange, a project site can also include a team mailbox, for unified communication about the project as it progresses.
When a project site is part of a site collection that is associated with Project Server 2013, it can also be used to capture issues, risks, and deliverables. The tasks list on the project site (or on a team site) can be added to the Project Web App for more robust project management functionality.

Saturday, 17 November 2012

The New "SPField.JSLink" property in SharePoint 2013

1 comment:
A New property "JSLink" of SPField has been Introduced in SharePoint 2013 with which you can now Control the Rendering (the presentation and validation) of any SPField (Custom or Out-of-box). 

You can Control the Rendering of any field in the List form and in the Views simply via assiging Custom JavaScript to the SPField.JSLink property of the that field."SPField.JSLink" property lets you specify any external JS file Containing any Client Rendering logic for a field type.

This property is available for Out-of-box Listview\Dataview webparts Where you simply set the property without modifying the webpart in SharePoint designer.So In addition to “Xsl Link” (Used to apply an external XSL to the listview webpart) that was available in Webpart properties in previous versions of SharePoint, you now have another option called “Js Link” where you can refer External JavaScript file to be used for the listview webpart. Just to be clear by external I mean a separate file not within the listview webpart. This can be uploaded to your Site asserts library or anywhere in your SharePoint site.

Edit the Listview Webpart's properties with “Edit Web Part” as shown in picture below.

Next in Webpart properties on right expand the last section “Miscellaneous” and scroll down. You would find “Js Link” as last option in Miscellaneous section.

Friday, 16 November 2012

What happened to SharePoint workspaces in SharePoint 2013

SharePoint workspaces is depreciaded but not Dead! You can Continue using it to sync SharePoint libraries and lists, including content hosted on SharePoint 2013 servers.

SharePoint 2013 sites don't provide direct access to SharePoint Workspace. There's no Site Actions menu, or Sync to SharePoint Workspace buttons on the ribbon. As a result, to create a SharePoint workspace from one of these sites, you must start in the SharePoint Workspace Launchbar, and directly reference the URL of the document library.

Additionally, because of a design change in SharePoint Server 2013 libraries, you must also install a SharePoint Workspace 2010 Update in order to sync these libraries in a SharePoint workspace.

To learn more about creating SharePoint workspaces from the SharePoint Workspace Launchbar, see Creating a SharePoint Workspace

You must know that SkyDrive Pro 2013 is the new Microsoft Office standard for syncing your SharePoint SkyDrive and SharePoint 2013 libraries to your computer.Start getting use to it.

Wednesday, 7 November 2012

New Features in SharePoint 2013 Developer Dashboard

No comments:
In SharePoint 2013 there is an Interactive addition in the new Developer Dashboard with which you can now View ULS logs (under a dedicated tab) for particular request.No more running around the admin teams or getting to SharePoint servers for ULS logs that you need.
Developer Dashboard in SharePoint 2013 improved to provide more information in more accurate way to track and debug issues with page rendering time.
  • Running in separate window to avoid affecting rendering of actual page
  • Detailed request information per page with chant view
  • Dedicated tab for ULS log entries for particular request
  • Additional detailed information included for request analyzing
  • Works by using dedicated WCF service (diagnosticsdata.svc)
  • You can enable (On) it or disable it (Off) by using  Powershell [Ondemand option is deprecated in SharePoint 2013]
  • Turn Off by default
  • Depends on "Usage and Health Data Collection Service Application" so make sure this service is created [Make sure Its job Timers are running]

Saturday, 3 November 2012

Web Analytics in SharePoint 2013

The new Analytics Processing Component in SharePoint Server 2013 runs different analytics jobs to analyze content in the search index and user actions that were performed on a site to identify items that users perceive as more relevant than others.

The new functionality for displaying content recommendations based on usage patterns uses the information from the analyses. By including recommendations on a page, you can guide users to other content that may be relevant for them. For example, you can guide users to popular items in a category or let them know that users who viewed this item also viewed another item.

The search recommendations framework works in the following way:

* User actions produce usage events. When users interact with a SharePoint Server 2013 website — for example, when they click a link, press a button, or view a document — their actions are stored as usage events.

* Usage events are counted and analyzed. The recommendations algorithm in the Analytics Processing Component counts and analyzes the usage events.

*  Information is added to the index. After processing in the Analytics Processing Component, the information is added to the search index and the Reporting database.

You can use search recommendations to do the following:

Add Recommended Items and Popular Items Web Parts to a site. In SharePoint Server 2013, you can display recommendations on a site by adding one or more Recommended Items Web Parts. You can configure the Web Part to display recommendations for the document or item that a user is viewing. For example, these recommendations can be displayed under the heading Users who viewed this document also viewed.

You can use the Popular Items Web Part to display the most popular items that satisfy a set of criteria. For example, these recommendations can be displayed under the heading
Most popular items in this category.
Get insights through reports. Information about usage events is displayed in Excel reports. You can use the reports to view user statistics to understand the traffic pattern on a website.

Act on insights. Based on the information in the reports, you can make decisions about how to fine-tune the website.

Monitor changes. The reports are updated based on the changes that are made, and you can monitor the effect of the changes.

Friday, 2 November 2012

Refiners and Faceted navigation SharePoint 2013

No comments:
Refiners and Faceted Navigation
Refiners are based on managed properties from the search index. Managed properties represent the specifications of the items in the catalog-enabled library or list — for example, Author, Date, Color, or Product Category. In a catalog scenario, you can add a Refinement Panel Web Part to a category page so that users can narrow the content as they browse through different pages.For example, in an Internet business scenario in which a catalog of mobile telephones is displayed, the managed property Color is set as a refiner. When a user views all mobile telephones in the catalog, all available colors are displayed in the Refinement Panel Web Part. When a user clicks a specific color, such as Gray, only mobile telephones with the color Gray are displayed. Similarly, in the scenario in which company events are displayed, the managed property Date is set as a refiner. In the Refinement Panel Web Part, users can see for which dates events are scheduled. When they click a particular date, they refine the results so that only events scheduled to occur on that date appear.

By using faceted navigation, you can configure different refiners for different terms in a term set. For example, in an Internet business scenario in which a product catalog is displayed, you can set the managed property Screen size as refiner for the term Computer, and the managed property Megapixels as refiner for the term Cameras. The faceted navigation guides users to content that is relevant for each specific category, and makes it easier and faster to browse through catalog content.

Saturday, 27 October 2012

SharePoint 2013 Search Authoritative and Non-authoritative Urls

No comments:
SharePoint 2013 Search has a lot of new Interactive Features like Spelling Correction Feature, "Result Types"  and "Name Suggestions" and one of the new feature that I was Introduced to today was Authoritative and Non-authoritative Urls. This is awesome for our company where we can prioritize the pages and URLs of documents that we would like users to see in order to get to all the links.

With Authoritative and Non-authoritative URls Admins can specify Pages\URLs which they called "Authoritative and non-authoritative URLs" that should be ranked higher or lower in Search results. 
An administrator can add authoritative and non-authoritative pages where they have options to specify "Most authoritative pages","Second-level authoritative pages","Third-level authoritative pages" and "Non-authoritative Sites".

To specify pages as authoritative or non-authoritative

  1. Verify that the user account that is performing this procedure is an administrator for the Search service application.
  2. In Central Administration, in the Application Management section, click Manage service applications.
  3. Click the Search service application.
  4. On the Search Administration page, in the Quick Launch, click Authoritative Pages.
  5. On the Specify Authoritative Pages page, in the Most authoritative pages box in the Authoritative Web Pages section, type the URLs of pages that are the most authoritative. Separate the URLs with returns so that there is one URL per line.
  6. In the Second-level authoritative pages box, type the URLs of any pages that should be seen as second-level.
  7. In the Third-level authoritative pages box, type the URLs of any pages that should be seen as third-level.
  8. In the Non-authoritative Sites section, in the Sites to demote box, type the URLs of any sites that you want to be ranked lower than all of the other sites. Type one URL per line.
    All URLs whose prefix matches the prefix of a URL in the Sites to demote box are demoted. Example: Entering http://archive/ demotes the rank of all URLs that begin with http://archive/.
  9. In the Relevance Ranking Analytics section, select the Refresh now check box to run the ranking analytics you have defined or that you have updated.
    If you clear the check box, ranking analytics run later according to a defined schedule.

Thursday, 18 October 2012

Spelling Correction Feature in SharePoint 2013

Another fabulous fetaure in SharePoint 2013 Search is "Spelling Correction Feature". This function is hosted in the Termstore. If a user enters a word in a search query that appears to be misspelled, the search results page displays query spelling corrections (under a "Did you mean?" text).

for example, if someone enters a query that contains the word "tarus", the query spelling correction would be "taurus". One of the good things here is that you can add terms to the Query Spelling Exclusions and the Query Spelling Inclusions list to influence how query spelling corrections are applied or not.
It takes up to 10 minutes for any changes to the Query Spelling Exclusions or the Query Spelling Inclusions list to take effect.

Monday, 15 October 2012

Why would you use CSWP over CQWP in SharePoint 2013

No comments:
CSWP is a great addition in SharePoint 2013.The Content Search Web Part (CSWP) is a Web Part introduced in SharePoint 2013 Preview that displays search results based on a search query and shows the results for that search query. Content Search Web Part displays search results in a way that you can easily format.

The big question is why would you choose CSWP over CQWP? CQWP and related SPSiteDataQuery can only search within the current site collection - the site collection “boundary” is a factor. CSWP on the other hand can search across the farm.

Sunday, 14 October 2012

SharePoint 2013 has PDF Support!!

No comments:
SharePoint 2013 now has Out of box PDF Support which is awesome for End Users.

Here are some of the Features -

* PDF icon is natively supported in SharePoint 2013 results

*  No need to install Adobe’s free PDF ifilter or Foxit PDF iFilter

* You can Open PDF file without saving them on your machine if you have Adobe Reader 10.0.2 or later is installed.

* SharePoint will try to open PDF file in the Adobe Reader and prompt user to either checkout & open or open the PDF file directly.

Saturday, 13 October 2012

What is the new "Result Types" in SharePoint 2013 Search

No comments:
In SharePoint 2013 Search has an new feature “Hover Panel” which shows you a "Preview" of an Item or document and some Metadata around it. This metadata or what you see in Preview pane can be customized with Result types.

Result Type determine what ‘type’ of result you’re looking at, and the correct hover panel will be shown based on those rules.

You can find Result types in site collection Site Settings under “Search”. For every Result Type Templte admins can specify Result Conditions & Result Actions for a Template.

Result Conditions or Rules - Determine what ‘type’ of result you will be looking at. For example a result condition could be something like

Match these types of content
Microsoft Word

Result Actions - The Correct hover panel that will be shown based on those rules. For example a Result Action for the above rule would be

Display results with this template
Word Item

Read more at SharePoint 2013 – The Concept of “Result Types” in Search

Thursday, 11 October 2012

SharePoint 2013 New Search Features

No comments:
SharePoint 2013 New Search Features

Content Search Web Part

In many ways this can be considered as the next generation of the previous Content Query Web Part. The Content Search Web Part displays content that was crawled and added to the search index. We can use category pages when we want to collect content that meets certain criteria or parameters. To understand correctly, take the example of an intranet scenario, all company events are maintained in a list that is shared as a catalogue. A query is issued from the Content Search Web Part to return all items from the search indexes that are specified in the query.

User interface improvements
In SharePoint 2013, without having to open each search result, users can quickly identify useful results in many ways.
 •Users can hover the pointer over a search result to preview the document content in the hover panel to the right of the result.
 •Users can quickly distinguish search results based on document types. For example, for Microsoft Office documents, the application icon is displayed in front of the title of the search result. We can customize it to add more icons
 •By default, certain types of related results are displayed in groups called result blocks. A result block contains a small subset of results that are related in a particular way. For example, results that are PowerPoint documents appear in a result block when the word presentation is one of the search terms.
•Search is personalized to each user. For example, results that the user previously clicked appear in query suggestions and are promoted in the result ranking, so that the user can find documents more quickly.

Site collection administrators and site owners can use display templates to customize the appearance of search results by using an HTML editor, and they can customize the behavior of search results by using JavaScript. They can specify display templates that determine how result types appear.
A search result, suggestion, or recommendation is more relevant when it better satisfies the intent of the person who issues the query. SharePoint Server 2013 improves relevance in areas such as cleanness of search results, phonology, and document parsing. We can discuss each one in detail.

New ranking models
SharePoint Server 2013 provides new ranking models for people search, intranet sites, and Internet sites. A ranking model determines and rank.

Content Analysis and user interaction
The search system determines the relevance of search results in part by how content is connected, how often an item appears in search results, and which search results people click. The new analytics component in SharePoint Server 2013 tracks and analyzes this information and uses it to continuously improve relevance.
Based on analytics information, site collection administrators and site owners can customize the user experience by adding Web Parts to display recommendations and popular items.

Query rules
Without any custom code, Search service administrators, site collection administrators, and site owners can help searches respond to the intent of users by creating query rules. In a query rule, you specify conditions and correlated actions. When a query meets the conditions in a query rule, the search system performs the specified actions to improve the relevance of the search results.

Result sourcesIn SharePoint Server 2010, scopes and federated locations provided ways to limit searches to a certain set of content or subset of search results. In SharePoint Server 2013, result sources replace scopes and federated locations. You create and use a result source to specify a location from which to get search results and to specify a protocol for getting those results.

Crawling Improvements
SharePoint Server 2013 includes many changes and improvements related to crawling content.
Continuous crawl
In SharePoint Server 2013, you can configure crawl schedules for SharePoint content sources so that crawls are performed continuously. Setting this option eliminates the need to schedule incremental crawls and automatically starts crawls as necessary to keep the search index fresh.

Host distribution rules removed
SharePoint Server 2013 does not use host distribution rules. Instead, Search service application administrators can determine whether the crawl database should be rebalanced by monitoring the Databases view in the crawl log.

Removing items from the search index
In SharePoint Server 2010, Search service application administrators could remove items from the search index by using Search Result Removal. In SharePoint Server 2013, you can remove items from the search index only by using the crawl logs.

Discovering Contents from unstructured content
We can configure the crawler to look for entities in unstructured content, such as in the body text or the title of a document. These entities can be words or phrases, such as product names. To specify which entities to look for in the content, you can create and deploy your own dictionaries. For companies, you can use the pre-populated company extraction dictionary that SharePoint Server 2013 provides.

Improved search schema
By defining crawled properties, managed properties, and the mappings among them, the search schema determines how the properties of crawled content are saved to the search index. Crawled properties and how these are mapped to managed properties define how to transform crawled content into managed properties. The search index stores the contents of the managed properties. The attributes of the managed properties determine the search index structure. SharePoint Server 2013 introduces new attributes that you can apply to managed properties, such as sortable and refinable. The sortable attribute reduces the time that is required to return large search result sets by sorting results before they are returned. The refinable attribute enables you to create a refiner based on a particular managed property.

Saturday, 6 October 2012

SharePoint 2013 - The new "Name Suggestions" Feature

No comments:
There are lot of Changes in SharePoint 2013 People Serach but one of them that looks fascinating is the Name Suggestions" Feature.

With "Name Suggestions" MS has Introduced a simple, easy, and intuitive way to find people by their names. "Word wheeling—typing a character(s) and seeing all the names starting with that character(s), is available on all names in the profile database, and therefore also in the People index.

The feature supports exact name matches and also supports "fuzzy" matches. With fuzzy name matches, the spelling is similar but not exact because of phonetic misspellings or typing errors

Fuzzy matching behavior is something where you Search for "numan" and it suggests you the result of "Belinda Newman".