Saturday, September 21, 2013

Configure Allow users to browser-enable form templates in SharePoint 2013

In this post we will discuss about how to Configure Allow users to browser-enable form templates in SharePoint 2013 through SharePoint central administration, as well as how we can enable using PowerShell.
Also you can check out my previous posts on:

- Change default error and successful message in infopath 2013

- Create workflow using SharePoint designer 2013 in SharePoint 2013

- Enable Disable developer dashboard in SharePoint 2013

Through SharePoint 2013 central administration we can configure "Allow users to browser-enable form templates".

Follow below steps:

- Open SharePoint 2013 Central Administration, then go to General Application Settings.

- For there select Configure general application and feature settings.

- Then in the General Application Settings Click on Configure InfoPath Forms Services.

- In Configure InfoPath Forms Services page, "User Browser-enabled Form Templates" section, Check on "Render form templates that are browser-enabled by users" check box and click on "Ok" button.

Also you can do this using PowerShell:

Run the below command in PowerShell:

Set-SPInfoPathFormsService -AllowUserFormBrowserRendering $true


InfoPath forms cannot be filled out in browser because state service connection is not configured error in SharePoint 2013

In this post we will discuss how to resolve the infopath 2013 error which comes when state service is not activated. Without state service the infopath will not open. To activate the service follow below steps:

- Open SharePoint central administration and then Launch Farm Configuration Wizard.

Then in the next step click on the Start the Wizard and this will open the list of the services page in the next page.

Then from the list, Select "State Service" check box. Then click on OK. It will activate the state service.

Also you can check out my previous posts on:

- Continuous Crawl in SharePoint 2013 search

- Installing or Uninstalling Features in SharePoint 2013

- Update website properties in SharePoint 2013 client object model


Tuesday, September 10, 2013

Add user to SharePoint security group using SharePoint client object model

In this post we will discuss how to add a user to a SharePoint security group using SharePoint client object model. Also you can check out my previous posts on:
- Add user to SharePoint group using SharePoint web service

- Submit data from Infopath form to SharePoint list using SharePoint object model

- Continuous Crawl in SharePoint 2013 search

To work with SharePoint 2013 client object model, we need to give reference to the below dlls:
- Microsoft.SharePoint.Client.Runtime.dll

- Microsoft.SharePoint.Client.dll

These dlls are located in %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\15\ISAPI.

Below is the full code to add user to SharePoint security group using SharePoint client object model

using Microsoft.SharePoint.Client;

ClientContext clientContext = new ClientContex("http://SiteURL");

web = clientContext.Web;
         
GroupCollection collGroup = web.SiteGroups;

Group oGroup = collGroup.GetById(5);        

UserCreationInformation userCreationInfo = new UserCreationInformation();

userCreationInfo.Email = "contact@onlysharepoint2013.com";

userCreationInfo.LoginName = @"DomainName\UserName";

userCreationInfo.Title = "Display Name";

User oUser = oGroup.Users.Add(userCreationInfo);

clientContext.ExecuteQuery(); 


Saturday, September 7, 2013

Keyword Query Language (KQL) enhancement in SharePoint 2013

Here we will see about enhancement in Keyword Query Language (KQL) in SharePoint 2013. Also you can check:
- New feature in SharePoint 2013 event receivers

- Continuous Crawl in SharePoint 2013 search

- Create workflow using SharePoint designer 2013 in SharePoint 2013

SharePoint 2013 now does not support FullTextSqlQuery. Also Microsoft advised not to use FAST Query Language (FQL), but still it is there in SharePoint 2013.
Microsoft now advised to use Keyword Query Language (KQL) and syntax to build their queries against a search engine.

Here are some queries and there result:

Onlysharepoint2013: This will return items containing Onlysharepoint or Onlysharepoint2013.

Onlysharepoint2013 Enjoysharepoint: This will return items containing Onlysharepoint2013 and Enjoysharepoint.

Onlysharepoint2013 OR Enjoysharepoint: This will return items containing Onlysharepoint2013 OR Enjoysharepoint.

"Onlysharepoint2013 Enjoysharepoint": This will return items containing exact phrase "Onlysharepoint2013 Enjoysharepoint".

Firstname:B : This will return all people whose Firstname starts with B.

Title:Onlysharepoint2013 IsDocument:1 - Returns all documents with "Onlysharepoint2013" in the title.

Author:Onlysharepoint2013 IsDocument:1 - Returns all documents authored by "Onlysharepoint2013".

Onlysharepoint2013 FileExtension:pdf - Returns PDF documents containing "Onlysharepoint2013".


Friday, September 6, 2013

Continuous Crawl in SharePoint 2013 search

Here we will see about Continuous Crawl in SharePoint 2013 search which is newly introduced in SharePoint 2013. Also you can check out some posts on:

- Create list using SharePoint 2013 client object model

- New master pages in SharePoint 2013

- OAuth in SharePoint 2013

In SharePoint 2010 there were 2 types of crawling: 1- Full Crawl 2- Incremental Crawl.

Full crawl focuses on almost everything about the content, whereas incremental crawls focus on picking up the changes in content or pushing the updated ACLs down to the affected items within the index.

Microsoft introduced a new type of crawl known as Continuous crawl.

To provide maximum freshness, continuous crawls focus on smaller changes and use the change logs to pick up those changes faster and in more efficient ways. Continuous crawls overlap each other, which means one continuous crawl doesn't hold up the other one in picking up the changes.

Continuous crawl can't be paused or stopped, only option is to disable it.


Result source in SharePoint 2013 search

We will discuss about Result Source in SharePoint 2013 search. Also you can check some posts on:

- Site Policies in SharePoint 2013

- Create update Delete list item using SharePoint 2013 object model

- Create workflow using SharePoint designer 2013 in SharePoint 2013

Result source is the new name for scopes and federated locations. Compared to SharePoint 2010, there are some changes in SharePoint 2013 result source.

Few Changes are:

- Result sources can be accessed from the search service application and in Search Settings at each site.

- In SharePoint 2010, FAST has been removed as an information protocol. There are 2 new protocols introduced.

1- Exchange SharePoint: Select Exchange protocol for results from Exchange.
2- Remote SharePoint: Select Remote SharePoint for results from a search service application hosted in a separate farm.

- Search Scope Rules has been removed, rather Now you can can specify a filter that will be applied to your queries using new Query Transformation settings. There is also a nice query builder that enables you to build your query transformations using a designer and sort and see the returned results in real time.

- The term scope is no longer used in SharePoint 2013 search and has been removed from the search UI.


Thursday, September 5, 2013

Design Manager in SharePoint 2013

Here we will discuss about Design Manager in SharePoint 2013 designer. Also you can check some posts on:

- Create SharePoint website using SharePoint 2013 client object model

- Advantages of SharePoint 2013 Apps

- Three tiers architecture in SharePoint 2013

SharePoint 2013 introduced a new feature called as Design Manager which helps customers customize SharePoint sites in a wizard-like approach.

Developers work with a designer or a design agency to brand SharePoint. First, the developer
receives the non-SharePoint branding assets (HTML, CSS, images etc) from the design agency. The design agency can create these files using any web design tool such as Dreamweaver or Microsoft Expression. The developer uploads the received files to SharePoint. Then, with a behind the scenes automatic process, SharePoint-specific assets (*.master & *.aspx) are generated. This process repeats until the branding task is complete. Then the developer exports the branding assets and creates a package (*.wsp) to deploy the custom brand to the production farm.


Content by Search (CBS) Web Part in SharePoint 2013

Here we will check about Content by Search (CBS) Web Part in SharePoint 2013. Also check out my previous posts on:

- Retrieve selected properties of website using SharePoint 2013 client object model

- Workflow activity in SharePoint 2013

- Hover panel in SharePoint 2013 search results

Content by Search (CBS) Web Part enables users to aggregate content directly from the search index. CBS is not constrained to one site collection. It's based on search, so it must to go beyond the site collection boundary. The query results in CBS may not be up to date.

CBS renders only major versions and cannot query content from site collections marked to be excluded from the search.

A query in CBS can be configured to aggregate content based on values on the page or within the URL.

CBS returns the results in raw XML format. Results can be styled using snippets of HTML and JavaScript instead of XSLT. These snippets are referred to as display templates in SharePoint 2013 and are stored in the Master Page gallery.


Installing or Uninstalling Features in SharePoint 2013

Here we will see Installing or Uninstalling Features in SharePoint. Also check out some posts on:

- Managed Meta Data in SharePoint 2013

- Get current user email by using SharePoint 2013 object model

- Change default error and successful message in infopath 2013

Run below command using PowerShell:

- Install-SPFeature FeatureFolderName

This will install the feature but we need to activate before using this.

To activate a feature, run the below Windows PowerShell command

Enable-SPFeature FeatureFolderName -Url http://URLOfSite

To uninstall a Feature, run the below Windows PowerShell command

Uninstall-SPFeature FeatureFolderName

To deactivate a feature, run the below Windows PowerShell command

Disable-SPFeature FeatureFolderName -Url http://URLOfSite


Managed Meta Data in SharePoint 2013

Here we will read about Managed Meta Data in SharePoint 2013. Also you can check:

- Create workflow using SharePoint designer 2013 in SharePoint 2013

- Create custom page layout in SharePoint 2013

- CAML designer for SharePoint 2013

There is not much changes in managed meta data in SharePoint 2013 compared to SharePoint 2010.

Like SharePoint 2010, SharePoint 2013 managed meta-data groups can be local or global. A global group is the one that can be used by any site collection connected to the same instance of the MMS application. A local group is one that although stored in the MMS application database is only available to a specific site collection.

In SharePoint 2010, users could reuse terms in the term hierarchy. After these terms were reused,
they could be updated and deleted in both the source and the referenced term sets. But in SharePoint 2013 introduced a new operation for terms: term pinning. A pinned term is just like a
reused term except it is read-only and cannot be modified (updated or deleted) in the referenced
term sets.

SharePoint 2013 now includes the ability to work with custom properties in terms and term sets through the browser, and CSOM APIs are added for remote clients. Custom properties are either shared or local.

Custom properties are either shared or local. Those available in all reused and pinned instances of the term are called shared custom properties. Local properties are only accessible for the term within the source term sets.


Tuesday, September 3, 2013

Site Policies in SharePoint 2013

Here we will check about Site policies feature in SharePoint 2013. Also you can check:

- Retrieve all SharePoint list in SharePoint 2013 client object model

- Advantages of SharePoint 2013 Apps

- Create workflow using SharePoint designer 2013 in SharePoint 2013

Through Site Policies you can control the life cycle of a SharePoint site. Suppose your requirement is that you want a site should automatically delete after 6 months of date of creation. Or you want it should start a workflow automatically and then it should delete the site.  In this type of schenarious site policies will be helpful.

In SharePoint 2010, you could create only policies attached to content types or at the site collection level. But in SharePoint 2013, an new link on the name of Site Policies is available under Site Collection Administration in Site settings page.

Site policy has various option like:
- 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


Twitter Delicious Facebook Digg Favorites More