SharePoint 2013 Search PDF Result Type with Previw in Browser

Friday, December 14, 2012

Search is the one of the most improved Feature that i found in SharePoint 2013. It’s Not only in Architecture or functionality. Even that Microsoft Improved Search User experience allot in SharePoint 2013. Now UI is more Informative and User Friendly. By Playing with SharePoint 2013 Search that t I Notice in SharePoint 2013 its Search quit Preview window. Where you can see immediately Preview the Search Result Items in Browser like Word Document. You don’t need to open them in any client app. To check is the same document that your look for. By just putting mouse over on the search result item it will give very nice small Hover Panel on right side of Search Results. Where you can see preview of your word,excel,powerpoint,html items and you can scroll down the document’s. it’s a Cool Feature and time saving. Another most important and requested feature for SharePoint 2013 Search to Provide PDF Search indexing by default OOB. So not need of IFilters for PDF Search. 

I was playing with SP15 Search then I notice SharePoint 2013 Search will not show me the PDF Documents in Preview mode Like documents word or excel. 

Then I jump into and try to some customized little bit. In SharePoint 2013 Search there is another very cool Feature in Search it’s called "Result Types" By default there is so many Result Types are there in your siteCollection and  you  can also create new by copying any existing one of the modified and create from scratch. To modified html and js files to display custom content in Preview window you need you find Display Templates under SPD2013 . Here i am trying to modify existing Result Types to Open Pdf in hover panel and display in Browser.


Open SharePoint Designer 2013 and open Site where you want this modification to be done. then navigate 
to All File>_catalogs>masterPage>Display templates>Search.

Find Item called   " item_PDF_HoverPanel.html " and right Click on Edit.

find Item
 then navigate the  Tag Div with ID  id="_#= $htmlEncode(id + HP.ids.content) =#_" data-displaytemplate="PDFHoverPanel". in Side this Tag just Past the Following Code. and save.

Refresh the Search Results and Mouse over again on PDF Item. if you will not find the Preview window so kindly install PDF plugin in your Browser 

By Usama Wahab Khan Happy SharePointing :)

Reference :


SharePoint 2013 Apps VS WebParts for Developers

Saturday, December 8, 2012

SharePoint 2013 Introduced App Model  Because of Software Market tends And Manage Solution without disturbing other tenants Especially in Online or Cloud scenarios. To meet this goal Microsoft Provide Great App Model for Developer to Build Apps on top of the SharePoint 2013. But mostly developer is used to develop their solution for Cloud by using visual WebPart in sandbox solution and farm based solution with visual webpart for on permission online sharepoint.  App Model quit bit similar from sandbox solution. But still are few recitations and changes between SharePoint WebPart and SharePoint Apps.  As a Developer feel bit restricted in this Model.As I like same felt same previously when 2010 sandbox . But it more secure as well because of any developer mistake it will not going to damage my SharePoint Site or Farm.

Difference  between WebPart and SharePoint App.

1.    OFFICE 356 AND MOST LIKE OTHER ONLINE SOLUTION FOR SharePoint would not allow Farm based Solution for web-Parts.

2.    Web Part has capability to use SharePoint Core Object by using code behind. 
3.    There is no code behind in SharePoint Apps. Especially for office 356 you create your solution without disturbing other tenant.

4.    You can create lists, libraries and other SharePoint Component.

5.    App have its own site-collection Site-Collection where app stores its list and data.
6.   SharePoint 2013 we have App Parts like Web Parts. App Part runs in IFrame by using the click jack technique. 
7.    The app runs in IFrame that why they cannot assess DOM. ITS HTML restriction. But it's really very cool feature if you app has some bed it will not disturb your site.

8.    If your app required any Service like the BCS. YOU HAVE TO ALLOW PERMISSION IN VS ON DEPLOYMENT TIME. WHEN USER WILL ADD APP. IT REQUIRED PERMISSION FROM USER TO ALLOW HIM TO ASSESS. THAT components OF SERVICE. LIKE books, stoical, taxonomy, Project, Reporting, List and Manage Rights Full Control., Read, Write, Managed. Give Specific Permissions for your apps. ReadMore
9.    SharePoint App has Page which ASPX page where app actually start-up page for the app.  
10.                 SharePoint also keeps its Assets with it. Like JavaScript and Images.

11.                 SharePoint 2013 App Features have only Web-scoped only for deployment.

12.                 SharePoint 2013 Web templates are available .But not site definitions. 


By Usama Wahab Khan