Break Permissions Inheritence for a docuemnt library in Sharepoint 2013

Breaking the Inheritence Option is a little hidden in SharePoint 2013. So here we have a trick on how to Break Inheritence and Set unique permissions for a docuemnt library.

Click on the "Library" tab  in the Ribbon and the click on "Share with"

Next click on "ADVANCED" in the pop-up.

 

Next Click on Stop Inheriting Permissions to set unique or Item level permission for the library.

Site Policies in SharePoint 2013

A site policy specifies the conditions under which to close or delete a site automatically. There are the following four options:

• Do not close or delete the site automatically
• Delete the site automatically
• Close the site automatically and delete the site automatically
• Run a workflow to close the site, and delete the site automatically

• Do not close or delete the site automatically. If a policy that has this option is applied to a site, the site owner must delete the site manually.


• Delete the site automatically. If a policy that has this option is applied to a site, the site owner may close the site manually, but the site will be deleted automatically. A policy that deletes the site automatically specifies a rule for when to delete the site, and has the following options:
  
  • What action triggers the site to be deleted, and how long to wait after the trigger occurs before deleting the site. The trigger can be either site creation or site closure. For example, you can create a policy that deletes a site three months after the site is closed, or a policy that deletes a site one year after the site is created.
    
  • Whether to have SharePoint 2013 send a notification email message to the site owner a specified amount of time before the site is scheduled to be deleted.
    
  • Whether to allow site owners to postpone deletion of the site.
  
  
• Close the site automatically and delete the site automatically. This option gives the same choices for how to delete the site automatically, and also requires you to specify how long after its creation time the site will be closed.


• Run a workflow to close the site, and delete the site automatically. This option gives the same choices for how to delete the site automatically, and also requires you to specify a workflow to run. When the workflow finishes running, SharePoint 2013 closes the site. You specify the name of the workflow, how long after the site is created to run the workflow, and whether to rerun the workflow periodically until the site is closed.
  A site policy can also specify that if it is applied to the root site in a site collection, when the root site is closed, the root site and all sub-sites become read-only.

SharePoint 2013 the New Continuous crawl

A new Crawl Option "Continuous crawls" has been Introduced in Search's Crawl Schedule category. Continuous crawls help to keep the search index and search results as fresh as possible.Continuous crawls run every 15 minutes by default although 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. Administrators should still configure full crawls as necessary.

When running, the crawler gets changes from SharePoint sites and pushes them to the content processing component.The document will get processed by the content processing component on the fly. No index has to be merged. Items appear in the search results right after they have been crawled.

Enabling continuous crawl has the following advantages:

• The search results are very fresh, because the SharePoint content is crawled frequently to keep the search index up to date.
  
• The search administrator does not have to monitor changing or seasonal demands for content freshness. Continuous crawls automatically adapt as necessary to the change rate of the SharePoint content.
  

SharePoint 2013 - New Feature "Content Recommendation"

Another awesome fetaure of SharePoint 2013 is "Content Recommendations". 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.

By including these recommendations on a page, you can guide users to other content that may be relevant for them. You can do this by adding Recommended Items and Popular Items Web Parts in the SharePoint 2013 site. 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.

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.

SharePoint 2013 - Unfollow SharePoint sites

I found this little tricky so I am writting a blog post about it. So how do you unfollow any site once you start following it.

To unfollow the site navigate to My sites (under NewsFeed) and click on “I’m following”. This will take you to the screen where it shows you all the “Sites you’re following”.




click on star next to the site to unfollow it.

What Language will you use for SharePoint 2013 Apps

So the question in the user group meeting was What Language will you use for SharePoint 2013 Apps?
Answer - It depends. here is the Chart that will help you decide.

• Representational State Transfer (REST): For scenarios in which you need to access SharePoint entities from client technologies that do not use JavaScript and are not built on the .NET Framework or Silverlight platforms, SharePoint 2013 Preview provides an implementation of a REST web service that uses the Open Data (OData) protocol to perform CRUDQ (Create, Read, Update, Delete, and Query) operations on SharePoint list data. In addition, nearly every API in the client object models has a corresponding REST endpoint. This enables your code to interact directly with SharePoint by using any technology that supports standard REST capabilities. To use the REST capabilities that are built into SharePoint 2013 Preview, your code constructs a RESTful HTTP request to an endpoint that corresponds to the desired client object model API. The client.svc web service handles the HTTP request and serves a response in either Atom or JavaScript Object Notation (JSON) format.


• .NET Framework client object model (.NET client OM): Almost every class in the core site and list server-side object model has a corresponding class in the .NET Framework client object model. In addition, the .NET Framework client object model also exposes a full set of APIs for extending other features, including some SharePoint Server 2013 Preview-level features such as ECM, taxonomy, user profiles, advanced search, analytics, BCS, and others.


• JavaScript client object model (JS client OM):SharePoint 2013 Preview provides a JavaScript object model for use in either inline script or separate .js files. It includes all the same functionality as the .NET Framework and Silverlight client object models. The JavaScript object model is a useful way of including custom SharePoint code in an app, because custom server-side code is not allowed in apps for SharePoint. It also enables web developers to use their existing JavaScript skills to create SharePoint applications with a minimal learning curve.

When you want to access data in your app from SharePoint, you have to use the APIs that the app provides.

SharePoint 2013 - Apps Related Errors

I am documents some the error that you can get while trying to Download and Install SharePoint Apps from the App store.


Error - "Sorry, there is a Problem with your Download"
Fix - Verify App Management Service is running on your WFE/app server.


Error -"Sorry we Couldn't determine which Apps to Show you. Please choose an available language from the options in the upper right corner."
Fix - Select the Laungage on the (no language selected) drop-down on upper right.


Error - "Sorry, apps are turned off. If you know who runs the server, tell Them to turn on the App Shared Service Management."
Fix - Verify App Management Service Shared service is running. Also Configure the Subscriptions setting service

Error - "Error occurred in deployment step 'Uninstall App for SharePoint' Value cannot be null. Parameter name value"
Fix - App has not Installed properly.Open the root site of your SharePoint website and click 'View Site Contents'. Here you will see your app installed.You need to remove the app by clicking on the ECB of the App and click the option Remove. After this you will get an error, just click retry. The app is now being uninstalled. After the uninstall try to remove the app again.


Error - "App domain must be configured prior to completing this operation"
Fix - You need to Configure an Isolated application domain to Install and run SharePoint 2013 App. Read more SharePoint 2013 App Error "App domain must be configured prior to completing this operation"


Error when you Turst an App - "Sorry, there was something wrong with the download. Try adding it again."
Fix -