Showing posts with label Sharepoint 2010. Show all posts
Showing posts with label Sharepoint 2010. Show all posts

Tuesday, August 15, 2017

All about SharePoint Licensing

SharePoint involves lots of components and hence the licensing of those components can be challenging . So the below video will help you grasp some of the terminology and practices involved in SharePoint Licensing. We have also look into different pain areas of software licensing and have tried to understand cost with small and medium farm setup


 Download the slide deck : https://drive.google.com/file/d/0B5Qpxy54-PeeWFdYZlRHRnViNnM/view?usp=sharing

Monday, June 1, 2015

BASICS OF CONTENT QUERY WEBPART: PART 1

CQWP has been around from ages but still I find it a most important component for any developer to rollup content over several different scopes, anywhere from a single list or library, to multiple list or libraries across an entire Site Collection.

CQWP is used for aggregating content from multiple data sources across your Web site, and then present it all in one place. On top of this you can present the information with your own custom UI by manipulating XSLT and CSS.

In this multi-part series I will be dwelling into various aspects of the CQWP

PART 1: Basics of CQWP

Part 1 : BASICS OF CONTENT QUERY WEBPART

In this part we will learn how to configure and customize the CQWP. This part is intended to the audience who have little or no experience with the CQWP.

  1. Adding CQWP to the Site
  2. Choosing Source or place from where data will be fetched.
  3. Learning the Additional Filters
  4. Presentation Section (Presenting the CQWP)
Adding CQWP to the Site

So let’s start by adding CQWP to our site.

  1. Open your SharePoint site and click the Site Actions drop-down and select Edit Page.
  2. Click on the Add a Web Part Link which open the Web part Gallery and then follow numbering to include the webpart.


  3. This will add the webpart and now to configure the webpart click “Edit the webpart” as shown

Choosing Source or place from where data will be fetched.
  1. Expand the Query Category in the Web Part Property Pane. This is basically used to choose your source and define list and content type based on that. There are three sources to choose from.
Learning the Additional Filters.

You can filter the data based on the columns/properties of the List. For E.g. I have a list “External News” with a column called “News Category” where I have category like “Political” and “Business”, now by default when I connect my list to CQWP then it will show all the items of the list as shown fig 4


So now if I want to show the “Political” news category then do as below, this will filter out the based on the “News Category” Political.



In SharePoint 2010, 2 new more advanced and dynamic way of filtering were introduced

PageFieldValue: Based on the field value present on the Page Layout, it will filter the items on the Content Query list. Let’s understand by example.
I have a Page Layout field called “Title” and based on the value of the Title I want to filter the “News Category” column of the List “External News”.
Now If I keep the page Title as “Business” and also changed the Content Query Filter as shown below then based on the page Title the data will be filtered from the List.



PageQueryString: This one I like the most. Let’s keep the same example. Define the filter as shown below [PageQueryString:] . Now using the variable name just pass the query string as shown below.
Using the query string parameter is better when you want to show different sets of results in a web part without having to make a new page for each different results set.


Presentation Section (Presenting the CQWP)
  1. Grouping and Sorting: You can select the column by which you want to group and sort the data.

    For e.g. I want to group the data based on the “News Category” column and sort based on “Created” column also u can tell whether you want to sort in Ascending or Descending order and limit the number of items to display.
  2. Styles: These define what information and how that information is displayed. I always feel styles section as a great value add to the CQWP. You can define style for the Group Style and Item Style, these styles are XSL templates, not CSS styles. You can create your own XSL templates. How to create styles will be part of the later series but just to show their power here is a small example.

    E.g. In the earlier list if I want to show the description of the title (In the list I have a column called Notes) and have the group heading as large text then this can be done as below.

Note: The “Fields to do display” section fields will change based on the “Item Style” you choose and you need to provide the column name from your list to display items.

I hope this walkthrough helps people configure and use the Content Query Web Part. Rest of the Article’s on other functionalities of the CQWP will be coming soon.

I'd be interested to hear and see examples of how people are using the web part. So, post your comments!

Sunday, April 29, 2012

Content Organizer in SharePoint 2010

The Content Organizer feature is a new routing feature that allows you to automatically route documents to different libraries and folders within a site collection. The document can be automatically routed to various document libraries based on the metadata.
Simply put it allows us to create rules that examine the content type and site columns of a document that was uploaded and move it someplace else.

It can also be used to do some housekeeping activities for the document Library for e.g. making sure that not any folder in a document Library contain more than specified no of records. If this happens it will create another folder and move the records to the new folder.

The requirement which came to me by a client was to develop a page where Legal department will upload the entire document and based on the metadata I will be pushing them in their respective document libraries. This will solve also the problem where sometime user don’t put the metadata on the document and just upload them. Hence now with this technique if they don’t provide the metadata the files will not reach the destination and will be just there sitting in the drop library.

How to Setup the Document Library

Now first we need to activate the Content Organizer Site Feature.


Once you activate this feature, there are three things get added to the site
-    A document Library called “DropOffLibrary”
-    Two new Links in Site Setting: Content Organizer Settings and Content Organizer Rules

The “Content Organizer Rules” link will take you to the rules List where you can add a new rule based on the content type and then you can specify condition based on the site column of the content type.

Lets see this with an Example.

Lets first see the high level diagram of what we are trying to achieve.
a)   We created a Content Type based on Document Content Type called “Support Request”.
       There we included new columns
                Support Name (Text Column)
                Support Type (Choice Column) whose option is IT Support and HR Support

b)    Then we created two documents Library based on the above content Type called HR Support and IT Support.

c)    Then we create Two Content Organizer Rule. Check out below how I have created “HR Document Rule”

d) In a similar way create a second rule called “IT Document Rule” where just change the condition to the one as shown below.

e) Now when we upload the document in a document library and from the Support Type dropdown column if we select HR Support the document will auto redirect to HR Support Library and we will get a similar message like the one shown below.


This is really a cool feature of SharePoint as we don’t require bothering where to push the document. If the rules are well placed just upload the document and it will reach its place.

Saturday, April 28, 2012

Creating hyperlink to display New List Form as Popup Dialog

Sharepoint 2010 Popup Dialogue
Someday back while designing a site I was required to have a New Form Link on the Home page and on clicking, it should show the popup Dialog window with the gray background.

Now first thing what came to my mind was to copy the same code from the “Add new Item” Link in List view. I was using IE to see the SharePoint site where I had developer Toolbar or in your case you case if you use Firefox can download firebug or just use view Source. So I Just pressed F12 on the page and the developer toolbar opened through which i coped the code of the link.


 After getting the link, remove the class and id attribute, so finally what I used is the snippet provided below. We can use the same code for any list. We just need to remove the List Id attribute with the correct List Id and the Site Name.

  <a onclick="javascript:NewItem2(event, &quot; http://Sitename /_layouts/listform.aspx?PageType=8&amp;ListId={88D74540-C80B-41BF-B325-EEAED6565385}&amp;RootFolder=&quot;);javascript:return false;" href="/_layouts/listform.aspx?PageType=8&amp;ListId={88D74540-C80B-41BF-B325-EEAED6565385}&amp;RootFolder=" target="_self">
Add New List Item
</a>

So the changes you need to make in the code before use are a)SiteName b)ListId.   In the below screenshot I have used with a content Editor web-part.   

I have added this screenshot showing how I added it to the CEWP and created the link

Wednesday, October 26, 2011

Sandboxed Solutions versus Farm Solutions

Sandboxed Solutions versus Farm Solutions


Why Sandbox came into Existence?

Each server in the farm can have multiple web applications running on it. A web application can in turn have one or more site collections, and a site collection has one or more sites. Farm solutions can impact the entire SharePoint system and are available to all site collections and sites in the farm. This is sometimes desirable, but sometimes can have undesired effects because a farm solution that is misbehaving can impact all sites and site collections in the system.
  • Sandboxed solutions are deployed at the site collection level rather than the farm level, so this lets you isolate a solution so it is only available to one site collection within the farm.
  • Sandboxed solutions also run in a separate process from the main SharePoint IIS web application
  • Process and the separate process is throttled and monitored with quotas to protect the SharePoint site from becoming unresponsive due to a misbehaving sandboxed solution.
  • It is worth mentioning that sandboxed solutions solve an organizational problem as well—in many organizations it is difficult to get permission to install a farm solution because of the possible impact that could have on the SharePoint system. System administrators in charge of running a Share-Point site have been reluctant in the past to allow custom solutions to run on their sites. With the advent of SharePoint 2010, there is now a robust system in place to monitor and throttle these custom solutions so that system administrators don’t have to worry about a custom solution bringing the entire SharePoint site down.
If all good with Sandbox then, why we require Farm Solution?

There are restrictions on the kinds of solutions you can build with a sandboxed solution.

The most significant restrictions disallow creation of
  • application pages
  • visual web parts
  • code-based workflows with a sandboxed solution.
So in the end, the choice between sandboxed and farm solutions should come down to whether or not you need to create an application page or a workflow with code in it. For these kinds of solutions, you should pick a farm solution. For all other solutions, pick a sandboxed solution. The only other reason to use a farm solution over a sandboxed solution is if you really have some code that needs to run at the web application or farm level, perhaps because it needs to interact with or move data between multiple site collections. In this case, you would create a farm solution as well.