SharePoint

At last I got time to play with Display Template. Though this is a simple implementation, this work provided better understanding of customizing the Display template for SharePoint Search results. The requirement is simple. By default, when you do search, it displays Results Count at the bottom of the page as shown below. Results Count in OOB Search Page The requirement is to shown the Results Count at the top just above search results as shown below: Results Count at top Let us see how do we achieve this. Let us first understand how default display template is related. Navigate to Results.aspx, edit page, and edit Search Results web part. You will see something like below. Search Results Web Part Properties If you closely look at the "Display Templates" section, there is something called "Results Control Display Template" and it is by default set to "Default Result". Now, we need to locate the file and modify it to our needs. For ...

Office App Model Samples (AMS) is a community driven project. This provides sample and patterns for SharePoint and Office App model development. The highlights of this project are: Provides ready to use code for common scenarios Code includes for Office365 and on-premise Provides Examples, Guidelines, and Reference Codes July 2014 release has Components, Samples, Scenarios, and Solutions Bundle of code can also be used for knowledge gain Another important note here is, we can also provide feedback to the team on scenarios which are not covered in the release. This project really speed up the learning curve and also saves lots of time in development. I've already downloaded the package and excited to go through these samples. Further reading: Office AMS codeplex project:  http://officeams.codeplex.com/ MSDN Blog:  http://blogs.msdn.com/b/vesku/archive/2014/07/01/office-ams-july-2014-release.aspx Happy Learning!

Pretty good collection of free eBooks on SharePoint as well as on other Microsoft technologies such as Windows, Office, Dynamics, PowerShell, SQL Server and more. Download and share the knowledge! http://blogs.msdn.com/b/mssmallbiz/archive/2014/07/07/largest-collection-of-free-microsoft-ebooks-ever-including-windows-8-1-windows-8-windows-7-office-2013-office-365-office-2010-sharepoint-2013-dynamics-crm-powershell-exchange-server-lync-2013-system-center-azure-cloud-sql.aspx

By making use of MS Word feature Quick Parts along with SharePoint Document Library columns, we can bring document metadata to the document as placeholders. In this blog post, I will cover the following: Connecting quick parts to library columns Limitations which should be kept in mind before deciding on using this feature In this example, I've used SharePoint 2013 and MS Word 2013. However, this should work for SharePoint 2010 and MS Word 2010 as well. Connecting MS Word Quick Parts to Document Library columns I've a document library and added a column Description of type Multi-line of text. Now go to Library Settings -> Advanced Settings, under Document Template, click on Edit Template link. Edit Template It opens MS Word. Once the document is open, under Insert tab, look for Quick Parts as shown below: Insert Quick Parts Click on this, and select Document Property and here you can see lots of fields. If you observe, you can also find Title and Descrip...

Sometimes, there are out of the box features which we tend to ignore and later when we do apply, we are more than happy about the feature which is readily available in SharePoint. One such feature is List View Style. I never thought I would write a post on this. However, whenever I spoke about this with users, people were excited to see the result. That prompted me to write this post. Instead of getting into only theory part, I will basically take use cases where these styles can be applied and also touch up on on some minor limitations with certain style. When you are creating/modifying a List view, you will get an option to select View Style. As shown below, there are 8 options available and Default is always set if you ignore this style. List of View Styles I will take typical Contact List and Announcement List to explian about these styles. Let us go one by one. Default: This view, as name suggest, is the default style in a view. This is one of the widely seen style ...

Community site template is a new feature in SharePoint 2013. It provides a forum experience in SharePoint. Microsoft also mentions about four types of Communities and membership permissions. Details can be found here . I'm producing the table mentioned in the above link, as this is the topic of today's post. TYPE DESCRIPTION PERMISSION APPROVAL SETTING Private community A community for sensitive information where you want to limit participation to specific users or groups. Grant Member permission only to those individuals or groups who are appropriate. None Closed community Everyone can view the content but only members with approved membership requests can contribute. Grant Visitor permissions to everyone. Require explicit requests to join. Enable access requests Open community with explicit membership Everyone can view the site and receives automatic approval upon joining. Grant Visitor permissions to everyone. Require explicit requests to join. Enable auto approva...

The question often arise on "View Only" permission about using this permission for restricting document download. And also on the difference between "Read" and "View Only" permissions. This post is to explain the difference between the two. Though my screens are taken from SharePoint 2010, it applies for SharePoint 2013 as well. Let us first quickly look at these two permissions as seen in SharePoint: As you can see from the description, users with View Only permission cannot download the documents, and this is applicable for document types with server-side handlers. What it means is, if you have enabled Office web app, Office documents such as Word, Excel, and PowerPoint are rendered in the browser itself. So, when user clicks on the document, it is rendered within the browser without getting downloaded to client. What it also means is, if the document is of type Text (.txt) or PDF, it is rendered in client (it is actually downloaded to user machine...