SP 2010, MOSS 2007, ASP.NET, SQL Server, SSRS, SSIS, jQuery, Javascript, WebServices, WCF, LINQ

SQL Server Reporting Services (SSRS) - Deployment

2012-03-17T14:14:00.003-07:00

Deploy Reports

Overview

In the prior sections we used Business Intelligence Development Studio (BIDS) to create some sample reports. BIDS has a preview capability which allowed us to render our report in the development environment. When we have completed a report we need tp deploy it so that other users can runit.

In this section we will show how to deploy reports using the following methods:

Business Intelligence Development Studio
Report Manager

In SQL Server 2005 Reporting Services you could also use SQL Server Management Studio to depploy reports.This functionality has been removed in SQL Server 2008.

You can deploy reports to a Sharepoint document library when you configure Reporting Services in Sharepoint Integration mode.We are not covering Sharepoint Integration in this tutorial.

Now let's continue on the next section to see how to deploy from BIDS.

BIDS

overview

BIDS provides the capability to deploy reports.This is very convinient since we use BIDS to design, develop and test our reports.In this section we will walk through report deployment uing BIDS.

Explanation

n order to deploy reports and data sources using BID,we need to specify some project settings. Right click on the project name in the Slution Explorer then select properties from the popup menu; you will see the dialog as shown below:

The following is a description of deployment settings:

OverwriteDataSources - SpecifyTrue or Flase;When you deploy using BIDS you probably want to choose False so that if the Data Sources already exists on the deployment target it does not get overwritten. The reasoning is that the connection strings in your development environment are probably different that your target deployment server.
TargetDataSourceFolder - the name of the folder where you ant to deploy your data sources; the default value is datasources.
TargetReportFolder - the name of the folder where you want to deploy your reports.The default value is the name of your project.
TargetServerURL - the URL of your deployment report server; use the format http://SERVERNAME/reportserver where SERVERNAME is the name of the server where you installed Reporting Services. "reportserver" is the default name; if you manually configured Reporting Services using the Reporting Services Configuration Manager then specify the name you used for the report server.

Deploying to http://sql2008test/reportserver

Deploying data source '/Data Sources/AdventureWorksLT'.

Warning : Cannot deploy data source AdventureWorksLT to

the server because it already exists and OverwriteDataSources

is not specified.

Deploying report '/SSRS 2008 Tutorial/ReportDesignerExample'.

Deploy complete -- 0 errors, 1 warnings

== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==

== Deploy: 1 succeeded, 0 failed, 0 skipped ==

After a successful deployment of our sample project, you will see the following on the Report Manager home page:

To navigate to the Report Manager use the URL http://SERVERNAME/reports; if you manually configured Reporting Services using the Reporting Services Configuration Manager then specify the name you used for the Report Manager, You can click on the Data Sources or SSRS Tutorials folders to see the data source or the reports.

Now let's continue on to the next sectionto see how to deploy reports using the Report Manager.

Report Manager

overview

Report Manager is the web-based application included wit Reporting Services that handles all aspects of managing reports.In this section we will walk through report deployment using the Report Manager.

Explanation

If you can deploy data sources and reports with BIDS, then why bother with using Report Manager? Probably the best answer is that those who develop reports may not have the necessary permissions to deploy those reports to the production server.When a report is ready for deployment, you man need to hand if off to a person who has the permissions to deploy to the production server ans that person doesn't want to use BIDS. Most admins are not developers and why they want is the ability to script out deployments or atleast use a tool that isn't developer-centric. Report Manager provides the capability to deploy data sources and reports by using a simple browsr-based interface.

To begin navigate to the Report Manager home by opening your browser and typing in the URL; e.g. http://SERVERNAME/reports, where SERVERNAME is the server where the Report manager is deployed. If you are working in your development environment and allowed the SQL Server installer to install and configure Reporting Services then you can use localhost as your SERVERNAME. After navigating to the Report Manager home you will see the following:

The folders shown in the above screen shot were created in the previous section where we discussed deploying data sources and reports using BIDS. Recall that the Reporting Services project has deployment settings which determine the folders for deploying data sources and reports. To deploy using the Report Manager we would create folders for our data sources and reports as shown above by clicking the New Folder button. Navigate to the new folder by clicking on it, then click the Upload File button to upload either a data source or a report.

When you click the New Folder button, the following dialog will be displayed:

Fill in the Name textbox; e.g. Report Manager Deployment Example and click OK. The Report Manager now displays the new folder:

Click on the Report Manager Deployment Example hyperlink to navigate to the folder. We are going to create a new data source and upload a report.

Typically when you deploy your data sources, the settings will be different than what you have in your development environment. Click the New Data Source button to create and configure your data source as follows:

The following are the main points about creating a data source:

• You have to enter the connection string; there is no helper dialog

• The Connect using option selected is Windows integrated security; this means the report executes using the Windows credentials of the caller; the caller must have at least read permission on the database

• The Credential stored securely in the report server option along with checking Use as Windows credentials when connecting to the data source is a good choice when you don't want to give the users running the report read permission on the database; rather you specify User name as DOMAIN\USERNAME and give just that account read permission on the database

After clicking OK to finish creating your data source, click the Upload File button to deploy a report. Fill in the dialog as shown below by navigating to the report that you want to deploy. I navigated to the folder where our BIDS project was saved and picked the file ReportDesignerExample.rdl (reports are stored in XML files with a .RDL extension):

After clicking OK to deploy the report, you can click on the report in the Report Manager to render it as shown below:

Configure Report Manager Security

Overview

Reporting Services implements a role-based security model that leverages the underlying Windows security model for authentication and authorization. You can administer Reporting Services security by using the Report Manager. By default only local administrators will have access to the Report Manager; you have to grant access to other users. There are two aspects to security: site settings and item level settings.

Now let's continue on to the next section to see how to configure site settings in Report Manager.

Site Settings

Overview

The first step in implementing Reporting Services security is to specify Site Settings. As the name implies Site Settings have to do with securing the Report Manager. We'll cover item level security in the next section where we talk about securing folders, reports, and data sources.

Explanation

To begin open your browser and launch the Report Manager. By default the Report Manager URL is http://SERVERNAME/reports unless you changed it by manually configuring Reporting Services. You will see the Report Manager home page as shown below:

Note in the upper right hand corner the Site Settings hyperlink; click it to navigate to the Site Settings page then click the Security hyperlink; the Site Settings Security page will be displayed as shown below:

Site settings offer two roles: System Administrator and System User. The default installation and configuration of Reporting Services adds the local administrators group to the System Administrator role. You can add any user or group that you want to administer the Report Manager to the System Administrator role. Any user or group that you want to allow access to the Report Manager content, you add them to the System User role. Click on the New Role Assignment button to display the New System Role Assignment page as shown below:

Fill in a user name or group using the format DOMAIN\USERNAME or DOMAIN\GROUPNAME. If your Reporting Services installation is on a stand-alone server (i.e. not a member of a domain) then substitute MACHINENAME for DOMAIN. Check the appropriate box to add the group or user to the System Administrator or System User role. Sometimes you may want to add the domain group Authenticated Users to the System User role; you still have to provide item level security settings which we will cover in the next section.

Item Level Settings

Overview

The second step in implementing Reporting Services security is to specify Item Level Settings. As the name implies Item Level Settings have to do with securing folders, reports, and data sources.

Explanation

Click the Properties hyperlink to navigate to the Security page as shown below:

Note that the local administrators group is already added to the Content Manager role; this is done by default. Click on the New Role Assignment button to display the New Role Assignment page as shown below:

There are a number of built-in roles available for item level security as shown above. The description provides the details of what each role is able to do. Wherever possible it's a good idea to assign role(s) to Windows groups rather than individual users. Specify the group as DOMAIN\GROUP or an individual user as DOMAIN\USER then check the appropriate role(s). If you want a group or a user to just be able to run reports, assign them to the Browser role.

When you create new folders in the Report Manager, they will automatically inherit the item level security settings of the parent folder. When you navigate to a folder, click on the Properties tab then click the Security hyperlink, you will see an Edit Item Security button. If you click Edit Item Security you will be asked whether to override the security as specified in the parent folder.

Typically setting item level security at the folder level is good enough. However you can set security at the individual item level. Navigate to the desired folder as shown below:

Click the Show Details button to display the detailed view as shown below:

Click the icon in the Edit column for an item then click the Security hyperlink on the Properties page; you will see the Security page as shown below:

Click the Edit Item Security button to override the security settings if necessary.

SQL Server Reporting Services (SSRS) - Reporting Services Components (Databases , Windows Service, Report Designer, Installation, BIDS, Creation Of Report)

2011-12-14T05:00:00.000-08:00

SQL Server Reporting Services (SSRS)
(Introduction)

OverviewSQL Server Reporting Services 2008 (SSRS) is a feature included in the SQL Server 2008 product. We use SSRS to design, develop, test, and deploy reports. SSRS was originally slated to be released with SQL Server 2005 but it wound up being released a little bit ahead of SQL Server 2005. SSRS leverages the Business Intelligence Development Studio (BIDS) developer tool for all aspects of authoring and deploying reports. BIDS is included with SQL Server 2008.

In this tutorial we will step through a number of topics that you need to understand to successfully build a report. Our high level outline is as follows:

Reporting Services Components
Install Reporting Services
Business Intelligence Development Studio (BIDS)
Install Sample Database
Create a Simple Report with the Wizard
Create a Simple Report with the Report Designer
Deploy Reports
Configure Report Manager Security

Reporting Services Components
(Introduction)

OverviewSQL Server Reporting Services 2008 (SSRS) is a full-featured application that provides report design, development, testing, and deployment. In this section we will introduce the main components of the product:

Databases
Windows Service
Report Designer

· Reporting Services Components - Databases

OverviewReporting Services creates and uses two SQL Server 2008 databases named ReportServer and ReportServerTempDB by default. The ReportServer database has tables to store reports, data sources, snapshots, subscriptions, etc. It is the repository for the reporting application data. The ReportServerTempDB database is used for temporary storage needs, as the default name suggests. When you allow the SQL Server 2008 installer to configure Reporting Services, these two databases are created automatically for you. If you want to create them manually, then you need to use the Reporting Services Configuration Manager. In this tutorial we assume that the SQL Server installer is used to configure Reporting Services.

Reporting Services Components - Windows Service

OverviewThe core of Reporting Services functionality is implemented as a Windows service. While an in-depth understanding of this implementation is not required to use Reporting Services, it is nonetheless interesting at least in terms of a high-level description.

ExplanationThe Reporting Services Windows service provides the following functionality as shown below in this diagram taken from Books on Line:

The following are the main points about the Windows service:

The HTTP listener is a new feature; prior versions of Reporting Services required Internet Information Server (IIS). With Reporting Services 2008 IIS is no longer required.
Report Manager is an ASP.NET application that provides a browser-based interface for managing Reporting Services. We will cover the Report Manager in a later section.
The Web Service is also implemented as an ASP.NET application; it provides a programmatic interface to Reporting Services. The Report Manager uses the web service. You can use the web service to create your own custom implementation of any feature provided by the Report Manager.
Background Processing provides the core services for Reporting Services.
The Report Manager, Web Service, and Background Processing are each implemented as separate application domains.

· Reporting Services Components - Report Designer

OverviewThe Report Designer provides the capability to design, develop, test and deploy reports. Report Designer is a developer-centric tool called Business Intelligence Development Studio (BIDS) that comes with SQL Server 2008. The 2008 version of BIDS has an updated and more intuitive user interface and many new charts and graphs for enhanced visualizations. We will cover BIDS in later sections of the tutorial.

For non-developers SQL Server 2008 has a new and enhanced version of Report Builder, which was first released with SQL Server 2005. We will not be covering Report Builder in this tutorial. You can get an introduction to the tool by reading one of our tips noted below.

Install Reporting Services

OverviewSQL Server Reporting Services 2008 (SSRS) is a feature included in the SQL Server 2008 product. To install SSRS you run the SQL Server 2008 SETUP.EXE program which guides you through the various installation and configuration options for the product. In this section we will discuss the installation and configuration options that pertain to installing SSRS.

ExplanationAs you proceed through the SQL Server 2008 installation process, you will reach the Feature Selection dialog. Click the checkbox for Reporting Services to perform the installation of SSRS as shown below under Instance Features:

Note that you should also probably check everything under Shared Features, especially Business Intelligence Development Studio as we use this tool to design, develop, test, and deploy reports.

Later in the SQL Server 2008 installation process you will reach the Reporting Services Configuration dialog as shown below:

Select the first option - Install the native mode default configuration. This will install SSRS and configure it for you automatically. SharePoint integrated mode disables the Report Manager and allows you to store reports in SharePoint document libraries; to run a report you simply click on it. The last option is useful where you want to configure the report server manually using the Reporting Services Configuration Manager.

You can begin using SSRS as soon as the SQL Server 2008 installation is complete, assuming you chose Install the native mode default configuration.

Business Intelligence Development Studio (BIDS)
(Introduction)

OverviewBIDS is the tool that we use to develop reports. It provides an intuitive interface based on Microsoft's Visual Studio product which has been used by developers for many years. The SQL Server 2008 version of BIDS has some nice enhancements to the user interface for designing, developing and testing reports. You will see these enhancements as we go through this tutorial.

BIDS is included with SQL Server. When you are running the SQL Server installer, you need to click the Business Intelligence Development Studio checkbox in the Shared Features section in order to install BIDS. You probably want to select all of the items in the Shared Features section. After completing the installation, you can launch BIDS from the Microsoft SQL Server 2008 program group.

Business Intelligence Development Studio (BIDS)
(Projects and Solutions)

OverviewThe BIDS paradigm for developing reports is based on the concept of projects and solutions. A project is a container for one type of object such as SSRS reports, web pages, SQL Server Integration Services packages, etc. Projects can be used to organize things in a meaningful way. For instance I could have a project for all reports used by the Accounting department, another project for Human Resource department reports, and another project for the Finance department reports.

A solution is a container for one or more projects. Think of a solution as the complete application that can be made up of a number of different types of projects such as a report project, SQL Server Integration Services project, a web project, etc.

In this section we will walk through creating an empty solution and adding a report project to that solution. In the sections that follow we will add reports to our report project.

ExplanationTo begin launch BIDS by selecting SQL Server Business Intelligence Development Studio from the Microsoft SQL Server 2008 program group. Click File, New Project on the top-level menu to display the New Project dialog. Click Visual Studio Solutions under Project Types, Blank Solution under Visual Studio installed templates, and enter the Name and Location as shown below:

Click OK to create a blank solution. Now we want to add a project to our solution. Remember a solution is just a container for one or more projects. By creating a blank solution, we can add multiple projects that make up the complete solution that we are building.

Click File, Add, New Project from the top-level menu to add a Report Server project to the solution. Fill in the Add New Project dialog as shown below:

At this point we have created a blank solution and added a Report Server project to the solution. Note that in the above screen shot Report Server Project Wizard is one of the options under Visual Studio installed templates. This option will create a project and immediately launch the Report Wizard. While this is okay, you probably don't want to create a new project for every report.

We are now ready to move on to our next section where we will install the sample database that we will use to build our reports.

Install Sample Database

OverviewWe will use the AdventureWorksLT sample database as the data source for the reports we build in this tutorial. The AdventureWorksLT database was chosen because it is small and the current SQL Server 2008 sample database requires that Full-Text Search be installed, the SQL Full-Text Filter Daemon launcher service is running, and FILESTREAM is enabled. These requirements just add extra work to get us going so we're going to use the slightly older sample database.

ExplanationThe AdventureWorksLT database is available for download from the following link on the Code Plex site: Microsoft SQL Server Product Samples: Database - Release:SQL Server 2005 SP2a. Click on the appropriate AdventureWorksLT link to download the installer program for your SQL Server environment: AdventureWorksLT.msi, AdventureWorksLT_x64.msi, or AdventureWorksLT_IA64.msi.

After downloading the appropriate version of the installer program, run it by double-clicking the .msi file. You will be prompted for the folder location to put the database and log files. For a default installation of SQL Server 2008 the folder to choose is:

C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA

Adjust the folder as necessary if you did not accept the default location during installation of SQL Server 2008.

When the installer program completes, you have to attach the database to your SQL Server database engine. Open SQL Server Management Studio, navigate to the Object Explorer, right click on Databases then select Attach from the menu as shown below:

The Attach Databases dialog will be displayed. Click the Add button, navigate to the AdventureWorksLT_Data.mdf file in the location you specified when you ran the installer program as shown below:

Click the OK button to attach the database.

Create a Simple Report with the Wizard

OverviewIn an earlier section we covered Business Intelligence Development Studio (BIDS), the tool that developers use to create reports. BIDS provides a Report Designer which allows you to define every aspect of your report. In addition BIDS provides a Report Wizard which will guide you through the steps to build a simple report. With the Report Designer you start out with an empty canvas; you define every aspect of the report yourself. When you are getting started with Reporting Services, the Report Wizard should be your first choice. Once you've built a report with the wizard, you can continue customizing it with the Report Designer. When you reach the point where you are comfortable defining every aspect of your reports and you want to build sophisticated reports and dashboards, then you should use the Report Designer.

In this section we will use the Report Wizard to build a simple report. We will walk through the following steps:

Launch the report wizard
Create a shared data source
Design a query
Select a report type
Design a table
Choose the table layout
Complete the wizard

· Launch the Report Wizard

OverviewThe Report Wizard guides you through the steps to build a simple report. In this section we will launch the report wizard and get going with creating our first report.

ExplanationIn the earlier section on Projects and Solutions, we created a blank solution and added a Report Server project to the solution. If necessary open the solution by clicking File, Open, Project/Solution from the top-level menu and navigating to the solution file; e.g. MSSQLTips_SSRS_2008_Tutorial.sln. The BIDS Solution Explorer shows our Report Server project along with Shared Data Sources and Reports nodes as shown below:

Right click on the Reports node and select Add New Report to launch the Report Wizard as shown below:

Note the checkbox "Don't show this page again". You way want to click it as there isn't much need to see this dialog every time you want to design a new report using the wizard. Click the Next button to create a data source for your report which we will cover in the next section.

Create a Shared Data Source

Overview
The Data Source contains the information necessary to retrieve the data we want to render on our report. Reporting Services can access data in relational databases, OLAP databases, and just about other any data source for which you have an ODBC or OLE DB driver.

When we create a Data Source we can specify it as shared which means it can be used by any report in the same project. As a general rule you probably want to create Shared Data Sources. If a Data Source isn't shared it just means that its definition is stored inside the report and it cannot be shared with another report.

In this section we will walk through the details of creating a Shared Data Source.

ExplanationAfter launching the Report Wizard you will be presented with the Select the Data Source dialog as shown below:

Our project does not have any Shared Data Sources yet so we do not have the option of selecting an existing Shared Data Source for our new report. Instead we will have to define a Data Source. We will have to supply the following:

Name - choose a descriptive name for this Data Source; we'll use AdventureWorksLT. Do not put any spaces in the name; if you do you will get an error message when you complete the wizard and your Data Source will not be created
Type - select from the available options in the dropdown list; the default value of Microsoft SQL Server is the correct one for the AdventureWorksLT database that we are using
Connection String - enter the connection string for your Data Source; usually you will want to click the Edit button to enter the details and have the connection string created for you
Edit button - rather than entering the connection string, click this button to display the Connection Properties dialog where you can enter some information and have the connection string created for you
Credentials button - click this button to display the specify Data Source Credentials dialog where you can specify the credentials to use when connecting to your Data Source
Make this a shared data source checkbox - click this checkbox to create a Shared Data Source; any report in the same project can the use this Data Source

Click the Edit button to display the Connection Properties dialog; fill in your Server name and select the AdventureWorksLT database as shown below:

The Server name is the one where your SQL Server database is deployed. If you are running a named instance of SQL Server, you will need to specify the Server name as SERVERNAME\INSTANCENAME. If you are running SQL Server locally you can specify localhost in place of SERVERNAME. You should click the Test Connection button to verify that you are able to connect to the database then click OK to close the dialog.

Click the Credentials button to display the Data Source Credentials dialog as shown below:

The default selection Use Windows Authentication (Integrated Security) is okay for our purposes. This means that Reporting Services will connect to the Data Source using the Windows credentials of the person running the report. Note that when your report is complete and you deploy the report and Data Source for others to use, you can select a different option if necessary. For now we'll stick with the default.

After completing the above steps, the Select the Data Source dialog will look as shown below:

Click Next to move on to the Design the Query dialog which we will discuss in the next section

Design the Query

Overview
The Design Query step of the Report Wizard allows us to specify what data we want to retrieve from our Data Source and render in our report. In this section we will walk through the details of defining a query to retrieve the data to render on our report.

ExplanationThe Design the Query step in the Report Wizard will display the dialog as shown below:

You can click the Query Builder button to graphically build your query or you can type your query directly into the Query string textbox. The following is an example of a query that you could type in:

SELECT

c.ParentProductCategoryName

, c.ProductCategoryName

, SUM(d.LineTotal) Sales

FROM SalesLT.Product p

JOIN SalesLT.vGetAllCategories c

ON c.ProductCategoryID = p.ProductCategoryID

JOIN SalesLT.SalesOrderDetail d

ON d.ProductID = p.ProductID

GROUP BY

c.ParentProductCategoryName

, c.ProductCategoryName

ORDER BY

c.ParentProductCategoryName

, c.ProductCategoryName

The above query will provide us with a sales summary broken down by product category. Copy and paste the query into the Query string textbox in the Design the Query dialog. Alternatively you could click the Query Builder button and graphically design the same or a similar query. The Query Builder dialog displays the Query designer that you are accustomed to seeing in products like Microsoft Access.

Click Next to move on to the Select the Report Type dialog which we will discuss in the next section.

Select the Report Type

Overview
The Select Report Type step of the Report Wizard allows us to choose from a Tabular or Matrix type of report. In this section we will discuss the details of these available report types.

ExplanationThe Select Report Type step in the Report Wizard will display the dialog as shown below:

The tabular report type is the traditional report with page headings, column headings, subtotals and totals running down the page. The matrix report type is one where we define the fields that go on the columns and rows. In addition the matrix report type provides interactive drilldown capabilities. We'll create a tabular report as this will provide a simple and familiar example.

Click Next to move on to the Design the Table dialog which we will discuss in the next section.

Design the Table

Overview
The Design Table step of the Report Wizard allows us to layout the available fields on our report choosing between Page, Group, and Details.

ExplanationThe Design Table step in the Report Wizard will display the dialog as shown below:

The Available fields list is populated based on the query that you defined in the previous step in the Report Wizard. Click on a field then click on the appropriate button where you want to put that field. Fill in the dialog as shown below:

The following is a description of the buttons in the above dialog:

Page - put a field in this list when you want to begin a new page when the value of the field changes; e.g. to start each ParentProductCategory on a different page
Group - group by the fields in this list
Details - the fields in this list appear in each row of the report

Click the Next button to move on to the Choose the Table Layout dialog which we will discuss in the next section.

Choose the Table Layout

Overview
The Choose Table Layout step of the Report Wizard allows us to choose a stepped or blocked layout and whether to include subtotals and enable drilldown.

ExplanationThe Choose Table Layout step in the Report Wizard will display the dialog as shown below:

The default of Stepped displays the groupings as shown above. Block moves things in a little closer which saves space, but it disables drilldown. Include Subtotals will provide intermediate totals based on groupings. Enable drilldown will initially hide details and allow expanding with a click on the plus icon.

Fill in the dialog as shown below:

Click the Next button to move on to the Chose the Table Style dialog which we will discuss in the next section.

Choose the Table Style

Overview
The Choose Table Style step of the Report Wizard allows us to choose from a number of different styles. This is a purely cosmetic choice; each selection provides a different color scheme.

ExplanationThe Choose Table Style step in the Report Wizard will display the dialog as shown below:

Choose a style from the list of available options the click the Next button to move on to the Completing the Wizard dialog which we will discuss in the next section.

Complete the Wizard

Overview
The Completing the Wizard step of the Report Wizard displays a summary of our choices from the previous dialogs.

ExplanationThe Completing the Wizard step in the Report Wizard will display the dialog as shown below:

You should provide a descriptive name for your report in the Report Name textbox; e.g. ReportWizardExample. You can click the Preview report check box if you would like to see what your report will look like. Scroll through the Report summary to review your choices. If there is something you want to change, click the Back button to revisit the completed dialogs.

Click the Finish button to have the wizard generate your report. You will now see your report in the Solution Explorer as shown below:

The report will also be displayed in the Report Designer. Click on the Preview tab to render your report. A portion of the report is shown below:

We're going to make a couple of changes to the report. Click on the Design tab; you will see the following:

We're going to put spaces between the words in the heading, make the columns a little wider, and change the format of the sales numbers. Here are the steps:

Click in the report heading between the t and W; add a space; do the same for d and E
Click in the ParentProductCategory cell, an Excel-like grid will appear, click between the cells at the top of the grid and drag to widen them; you will see the cursor change to <--> when you hover between the cells
Click inside the [Sum(Sales)] column, locate Format in the Properties window and type C0; this will format the cell as currency with no decimals. If you don't see the Properties window, click the top-level View menu then select Properties Window of click F4. Repeat for the [Sales] column.

After making these changes the report design should look like this:

Click on the Preview tab to display the report:

You can click on the + icon to the left of the Parent Product Category Names to drilldown to Product Category Name details as shown below:

This completes our tutorial section on the Report Wizard.

Create a Report using the Report Designer

OverviewIn the prior section we created a report using the Report Wizard in Business Intelligence Development Studio (BIDS). In this section we will create a report from scratch using the Report Designer in BIDS. With the Report Designer you start out with an empty canvas; you define every aspect of the report yourself. The Report Designer allows you to create sophisticated reports and dashboards.

In this section we will complete the following steps in the Report Designer to build a simple report:

Add a new report to our project
Create a shared data source
Create a Dataset
Configure a Table

The following screen shot shows the report that we will build as rendered in the Report Manager:

The above report is based on the same query that we used in the earlier Report Wizard section. The plus sign icon to the left of the value in the Parent Product Category column allows us to drilldown to the Product Category details.

Now let's continue on to the next section and begin to create our report.

Create Report

OverviewThe first step in creating a report is to add a new report to our project.

ExplanationIn the earlier section on Projects and Solutions, we created a blank solution and added a Report Server project to the solution. In the previous section we added a new report by stepping through the Report Wizard. The BIDS Solution Explorer shows our Reports project along with the Shared Data Source and ReportWizardExample that we created in the previous section:

Right click on the Reports node then select Add, New Item which will display the Add New Item - Reports dialog; fill in the dialog as shown below:

Click the Add button to add a new report to your project. Your new report will be displayed in the Report Designer. Let's spend a minute to review the Report Designer before we continue with our task of creating a new report from scratch.

There are three parts of the Report Designer which you will be using:

Design Surface - palette where you layout your report
Report Data - allows you to define Data Sources, Datasets, Parameters and Images; allows you to access a group of built-in fields like Report Name, Page Number, etc. You will drag and drop items from this area onto the design surface.
Toolbox - contains the Report Items that you drag and drop onto the design surface; e.g. Table, Matrix, Rectangle, List, etc.

Whenever you add a report to your project or open a report the design surface will be displayed. After adding a report you will see the following blank design surface:

You can display the Report Data and Toolbox areas by selecting them from the top-level View menu if they aren't shown. The Report Data and Toolbox are used a lot so I like to position them to the left of the designer. The Report Data area is shown below:

Create a Shared Data Source

OverviewWe discussed the Shared Data Source in the earlier section on using the Report Wizard to create a new report. The Data Source contains the information that Reporting Services needs to retrieve the data that we want to render on our report. A Shared Data Source is one that can be used by any report in the same project. In this section we will create a Shared Data Source.

ExplanationTo create a Shared Data Source click on the New button in the Report Data area then select Data Source from the menu as shown below:

The Data Source Properties dialog will be displayed as shown below:

The first thing to do is to provide a name; enter AdventureWorksLT in the Name textbox. Since we already defined a Shared Data Source in the earlier section on using the Report Wizard to create a new report, click the Use shared data source reference radio button and select AdventureWorksLT from the dropdown list. The Data Source Properties dialog is shown below:

At this point we are done. If you need to create a new Shared Data Source, you would click the New button and complete the Shared Data Source Properties dialog. This is essentially the same thing we did back in the Report Wizard section of the tutorial.

We can now see our Shared Data Source in the Report Data area as shown below:

We are now ready to continue on to the next section and create a Data Set.

In the screen shot above Report Data and the Toolbox share the same area of the screen; click on the tab at the bottom to switch between them. The Toolbox contains the following elements that you will drag and drop onto the design surface:

Note in the heading of Report Data and the Toolbox there is a push pin icon. Clicking this toggles between showing the tab and hiding it by putting a button that you can hover over to display the tab.

You can customize what you see in the report designer as well as position it however you like. Click on the Report Data or Toolbox heading and you can drag it around and position it.

At this point let's continue on to the next section and create a Shared Data Source.

Create a Data Set

OverviewA Data Set contains a query that Reporting Services uses to retrieve the data for our report. This query could be a SQL statement like we used in the Design the Query step of the Report Wizard section; it could also be a stored procedure that we execute. In this section we will define a new Dataset by using the same query that we used earlier in the Report Wizard section.

ExplanationTo create a Dataset right click on the AdventureWorksLT Shared Data Source that we created in the previous section and select Add Dataset from the menu as shown below:

The Dataset Properties dialog will be displayed as shown below:

The first thing to do is to provide a name; enter Main in the Name textbox. Since we only have one Shared Data Source in our project, it will be selected automatically in the Data source dropdown. To define our query we could click the Query Designer button and do it graphically or we could type in the query as we did in the Report Wizard section. Instead click the Import button which will initially display the familiar Open File dialog; navigate to the report that we created earlier in the Report Wizard section of the tutorial as shown below:

Click OK to display the Import Query dialog as shown below:

The above dialog displays the Datasets and their queries from the report. Our earlier report has only one Dataset so just click the Import button. If the report had multiple Datasets, you could choose the Dataset from the list on the left.

The Report Data area now shows our new Dataset and the list of available fields as shown below:

We are now ready to continue on to the next section to configure a Table for our report layout.

Design Report Layout

OverviewThe Toolbox contains a number of Report Items that you drag and drop onto the design surface when creating a report. The Table provides the traditional report layout where you render data in a fixed number of columns and a variable number of rows. In this section we will use the Table to define the same report layout that we used earlier in the Report Wizard section.

ExplanationTo add a Table to the design surface, simply click Table in the Toolbox then drag and drop it onto the design surface. The design surface should look like this:

Recall from our previous step where we created a Dataset; the Report Data is shown below:

Drag and drop the ProductCategoryName and Sales fields (one at a time) onto a column of the Data row of our Table as shown below:

Click the Preview tab to render the report; a portion of the rendered report is shown below:

Click on the Design tab and focus on the Row Groups at the bottom as shown below:

We want our report to show the ParentProductCategory broken down by the ProductCategory. Click the arrow on the (Details) line shown above then click Add Group, Parent Group; fill in the Tablix group dialog as shown below:

The Table now looks like this:

Right click on the gray border above the empty column and select Delete Columns from the menu. Click on the Group1 cell and change the text to Parent Product Category. Click and drag the gray border above the column headings to make them a little wider. Click the Preview tab to render the report:

At this point we are almost done; we need to add Parent Product Category totals, drilldown capability to show/hide the Product Category details, a grand total, and some general cosmetic cleanup. Click on the Designer tab to continue.

To add the Parent Product Category totals, hover the mouse over the empty cell in the Sales column on the ParentProductCategoryName row; a little icon will appear; click the icon and select Sales from the popup menu. You will see the expression [Sum(Sales)] as shown below:

To add the drilldown capability, right click on the gray border on the bottom row in the designer and select Row Visibility from the popup menu. Fill in the Row Visibility dialog as shown below:

The above settings will initially hide the Product Category details and add the plus sign icon next to the Parent Product Category to toggle the drilldown. The name Group1 was assigned when we added the Parent Product category group. Click the Preview tab to render the report:

Click the Design tab then click the arrow on the Details line inside the Row Groups area; select Add Total, After from the popup menu. You will now see a row after the detail row; edit the blank cells on the total lines to specify a description as shown below:

Finally for the cosmetic changes, drag and drop a text box above the table and provide a heading for the report. Click in the Sales cells and specify C0 (i.e. Currency with no decimals) as the Format property in the Properties window (click View the Properties on the top-level menu if you don't see the Properties window). Click Preview to see the completed report:

This completes the section on creating a report from scratch. We are now ready to continue on to the next section to discuss the options for deploying reports.

SharePoint 2010: ECMA Script Client OM & Examples

2011-11-23T19:40:00.001-08:00

SharePoint 2010: ECMA Script Client OM

Before going to the post please read this post SharePoint 2010 : Client OM to get the more information related to SharePoint Client OM.

Few points to notice about ECMAScript Client OM:

ECMAScript Client OM can only be used in SharePoint sites. So you can’t use this OM in an asp.net site to access SharePoint resources deployed in another URL as this is cross-site scripting and not allowed.
You can’t use this OM in a SharePoint site to access resources in different SharePoint sites (i.e., different url’s). For example, from mysite.mysp.com you can access resources in yoursite.yoursp.com using ECMAScript client OM. This is also cross-site scripting.
You can use JQuery with ECMAScript Client OM and for this you don’t need to do some extra work. All you need to do to use JQuery is to add reference to JQuery.js file and start using JQuery.
You can use this ECMAScript Client OM in web part pages or application pages (aspx pages) by referencing a javascript file (SP.js). You don’t need to add reference to the file manually rather use <SharePoint: ScriptLink Name=”sp.js” ………. />. The file is located on the path “Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS”
To update with JavaScript, you need to add a FormDigest tag in your page for security purpose.

Use ECMAScript Library: A Sample program

At first use Visual Studio 2010 to create a SharePoint web part project. As a result, VS2010 will open a ascx control for you on the designer.

1. Add reference to js file:

To use Client OM, add an entry like below in your web part ascx control. For your information, there’s an debug version of the sp.js called sp.debug.js which you can use for debugging but should not be used in production.

<SharePoint:ScriptLink Name="SP.js" runat="server" OnDemand="true"

    Localizable="false" />

Here, OnDemand means whether the sp.js file need to be loaded on demand (not in page load) or not.

2. Add FormDigest tag:

If your code modifies SharePoint content add a FormDigest control inside your page. The FormDigest add a security token inside your page based on user, site and time. Once the page is posted back the security token is validated. Once the security token is generated it’s valid for a configurable amount of time. Add the FormDigest inside <form>…</form> tag, as shown below:

<SharePoint:FormDigest runat="server" />

For more information on FormDigest follow the links below:

3. Use Client OM to retrieve data:

Now you can use SharePoint ECMAScript library. Let’s dissect the code snippet below. The first thing in using this library is that you need to get the ClientContext (just like SPContext). Then the context.get_web returns the current web (just like SPContext.Current.Web). Then client context’s load method is invoked passing the web object. Then the executequery method is invoked asynchronously passing two functions: onSuccess and OnFailed which will be called on success and fail correspondingly.

<script type="text/javascript">

    function getWebProperties() {

        var ctx = new SP.ClientContext.get_current();

        this.web = ctx.get_web();

        ctx.load(this.web);

        ctx.executeQueryAsync(Function.createDelegate(this, this.onSuccess),

            Function.createDelegate(this, this.onFail));

    function onSuccess(sender, args) {

        alert('web title:' + this.web.get_title() + '\n ID:' + this.web.get_id() +

            '\n Created Date:' + this.web.get_created());

    function onFail(sender, args) {

        alert('failed to get list. Error:'+args.get_message());

</script>

By calling getWebProperties method from any web part, you can get the current web’s title, id and creation date.

4. Load minimal data you need:

In the above code snippet, the Ctx.load method is invoked with only one parameter (web). The load method will load all properties of the web object. But we are only using Id, Title and Created Date properties. If you know which properties you are interested in, you can pass the properties names in the load method and only those properties will be loaded. For example the following load method will return only ID, Title and Created Date.

ctx.load(this.web,'Title','Id','Created');

Remember, here the properties names are properties of SPWeb. You need to pass Title instead of title. The properties name uses CAML casing. You can get the full lists of ECMAScript namespaces, object, properties following the link on MSDN. The document is not final yet and may be changed.

You can also look into the sp.debug.js file in the folder “Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS”, to get an idea of objects, properties and methods of ECMAScript Client OM.

5. Execute your JavaScript function after sp.js is loaded:

Sometimes you may need to execute your JavaScript (that uses ECMAScript Client OM) on page load in the browser. But since your JavaScript is using sp.js file and if the sp.js file is not loaded yet (since to lazy loading nature of sp.js), when your custom JavaScript will be executing, you’ll get your JavaScript function not executed. In this case you need to make sure your JavaScript code runs after sp.js finishes loading. You can do so by putting your JavaScript method call inside a js function as shown below:

ExecuteOrDelayUntilScriptLoaded(myjsfucntion, "sp.js");

Putting your JavaScript function (i.e., myjsfunction) inside the ExecuteOrDelyUntilScriptLoaded method delays your method call until the sp.js file is loaded.

6. Update with ECMAScript Library:

You can use the Client OM to update SharePoint contents. The following code snippet shows how to update web title.

<script type="text/javascript">

    function updateTitle() {

        var ctx = new SP.ClientContext.get_current();

        this.web = ctx.get_web();

        web.set_title('UpdatedTitle');

        this.web.update();

        ctx.executeQueryAsync(Function.createDelegate(this, this.onUpdate),

            Function.createDelegate(this, this.onFail));

    function onUpdate(sender, args) {

        alert('title updated');

    function onFail(sender, args) {

        alert('failed to update title. Error:'+args.get_message());

</script>

By calling the updateTitle method from any web part or SharePoint application pages, you can change the title of current web site (where the web part or application page is deployed). For your information, in ECMAScript Client OM, to get an property use get_propertyName and to set a property use set_propertyName. To update list with ECMAScript library you need to add FormDigest tag.

Use JQuery with ECMAScript

You can use JQuery with ECMAScript without any conflict. As usual, you need to add jquery.js file reference to your page/web part or in master page. Then you can use JQuery as like normal asp.net applications. But make sure that if you need to execute any JavaScript function on page load event, you put this inside ExecuteOrDelayUntilScriptLoaded function.

Deployment Consideration

SharePoint provides two sets of JavaScript file: minified and unminified/debug version.

For example sp.js file is minified and sp.debug is minified and debug version.

The default master page in SharePoint has a scriptmanager in the page and whose ScriptMode is set to auto, as a result the minified version of js file loaded.

If you want to use debug version you can add the <deployment retail="false" /> in the <system.web> section of the web.config. In the production you need to remove this entry to make sure minified version is used.

ECMA SharePoint 2010 Code Examples:

1. To Create A List

<script type="text/javascript">

var clientContext = null;

var web = null;

ExecuteOrDelayUntilScriptLoaded(Initialize, "sp.js");

function Initialize()

clientContext = new SP.ClientContext.get_current();

web = clientContext.get_web();

var itemCreateInfo = new SP.ListItemCreationInformation();

var listCreationInfo = new SP.ListCreationInformation();

listCreationInfo.set_title('My Custom Generic List');

listCreationInfo.set_templateType(SP.ListTemplateType.genericList);

this.oList = web.get_lists().add(listCreationInfo);

clientContext.load(oList, 'Title', 'Id');

clientContext.executeQueryAsync(Function.createDelegate(this, this.onListCreateSuccess),

Function.createDelegate(this, this.onQueryFailed));

function onListCreateSuccess(sender, args) {

         alert("List title : " + this.oList.get_title() + "; List ID : "+ this.oList.get_id());

function onQueryFailed(sender, args) {

         alert('request failed ' + args.get_message() + '\n' + args.get_stackTrace());

}</script>

2. To Create A Site

<script type="text/javascript">

var clientContext = null;

var web = null;

ExecuteOrDelayUntilScriptLoaded(Initialize, "sp.js");

function Initialize()

clientContext = new SP.ClientContext.get_current();

web = clientContext.get_web();

var webCreateInfo = new SP.WebCreationInformation();

    webCreateInfo.set_description("Description.");

    webCreateInfo.set_language(1033);

    webCreateInfo.set_title("SharePoint and .NET");

    webCreateInfo.set_url("SharePoint");

    webCreateInfo.set_useSamePermissionsAsParentSite(true);

    webCreateInfo.set_webTemplate("BLOG#0");

    this.oNewWebsite = this.web.get_webs().add(webCreateInfo);

    clientContext.load(this.oNewWebsite, 'ServerRelativeUrl', 'Created');

clientContext.executeQueryAsync(Function.createDelegate(this, this.onCreateWebSuccess),

Function.createDelegate(this, this.onQueryFailed));

function onCreateWebSuccess(sender, args) {

         alert("Web site url : " + this.oNewWebsite.get_serverRelativeUrl());

function onQueryFailed(sender, args) {

         alert('request failed ' + args.get_message() + '\n' + args.get_stackTrace());

}</script>

3. To delete a Site

<script type="text/javascript">

var clientContext = null;

var web = null;

ExecuteOrDelayUntilScriptLoaded(Initialize, "sp.js");

function Initialize()

clientContext = new SP.ClientContext.get_current();

web = clientContext.get_web();

this.website = web.get_webs().getByTitle('jayakrishnaakkiraju.blogspot.com');

website.deleteObject();

clientContext.executeQueryAsync(Function.createDelegate(this, this.onSiteDeleteSuccess),

Function.createDelegate(this, this.onQueryFailed));

function onSiteDeleteSuccess(sender, args) {

         alert("site deleted");

function onQueryFailed(sender, args) {

         alert('request failed ' + args.get_message() + '\n' + args.get_stackTrace());

}</script>

4. To delete a List

<script type="text/javascript">

var clientContext = null;

var web = null;

ExecuteOrDelayUntilScriptLoaded(Initialize, "sp.js");

function Initialize()

clientContext = new SP.ClientContext.get_current();

web = clientContext.get_web();

this.list = web.get_lists().getByTitle('My custom generic list');

list.deleteObject();

clientContext.executeQueryAsync(Function.createDelegate(this, this.onListDeleteSuccess),

Function.createDelegate(this, this.onQueryFailed));

function onListDeleteSuccess(sender, args) {

         alert("list deleted");

function onQueryFailed(sender, args) {

         alert('request failed ' + args.get_message() + '\n' + args.get_stackTrace());

}</script>

5. To delete a ListItem

<script type="text/javascript">

var clientContext = null;

var web = null;

ExecuteOrDelayUntilScriptLoaded(Initialize, "sp.js");

function Initialize()

clientContext = new SP.ClientContext.get_current();

web = clientContext.get_web();

this.list = web.get_lists().getByTitle('My custom generic list');

this.oListItem = list.getItemById(1);

oListItem.deleteObject();

clientContext.executeQueryAsync(Function.createDelegate(this, this.onListItemDeleteSuccess),

Function.createDelegate(this, this.onQueryFailed));

function onListItemDeleteSuccess(sender, args) {

         alert("list item deleted");

function onQueryFailed(sender, args) {

         alert('request failed ' + args.get_message() + '\n' + args.get_stackTrace());

}</script>

6. To Load List Data

<script type="text/javascript">

var clientContext = null;

var web = null;

ExecuteOrDelayUntilScriptLoaded(Initialize, "sp.js");

function Initialize()

clientContext = new SP.ClientContext.get_current();

web = clientContext.get_web();

this.list = web.get_lists().getByTitle("Images");

clientContext.load(list, 'Title', 'Id');

clientContext.executeQueryAsync(Function.createDelegate(this, this.onListLoadSuccess),

Function.createDelegate(this, this.onQueryFailed));

function onListLoadSuccess(sender, args) {

         alert("List title : " + this.list.get_title() + "; List ID : "+ this.list.get_id());

function onQueryFailed(sender, args) {

         alert('request failed ' + args.get_message() + '\n' + args.get_stackTrace());

}</script>

7. To load List Items Data

<script type="text/javascript">

var clientContext = null;

var web = null;

ExecuteOrDelayUntilScriptLoaded(Initialize, "sp.js");

function Initialize()

clientContext = new SP.ClientContext.get_current();

web = clientContext.get_web();

var list = web.get_lists().getByTitle("Pages");

var camlQuery = new SP.CamlQuery();

var q = '<View><RowLimit>5</RowLimit></View>';

camlQuery.set_viewXml(q);

this.listItems = list.getItems(camlQuery);

clientContext.load(listItems, 'Include(DisplayName,Id)');

clientContext.executeQueryAsync(Function.createDelegate(this, this.onListItemsLoadSuccess),

Function.createDelegate(this, this.onQueryFailed));

function onListItemsLoadSuccess(sender, args) {

         var listEnumerator = this.listItems.getEnumerator();

         //iterate though all of the items

         while (listEnumerator.moveNext()) {

             var item = listEnumerator.get_current();

             var title = item.get_displayName();

             var id = item.get_id();

            alert("List title : " + title + "; List ID : "+ id);

function onQueryFailed(sender, args) {

         alert('request failed ' + args.get_message() + '\n' + args.get_stackTrace());

}</script>

8. To load Site data

<script type="text/javascript">

var clientContext = null;

var web = null;

ExecuteOrDelayUntilScriptLoaded(Initialize, "sp.js");

function Initialize()

clientContext = new SP.ClientContext.get_current();

web = clientContext.get_web();

clientContext.load(web, 'Title');

clientContext.executeQueryAsync(Function.createDelegate(this, this.onSiteLoadSuccess), Function.createDelegate(this, this.onQueryFailed));

function onSiteLoadSuccess(sender, args) {

         alert("site title : " + web.get_title());

function onQueryFailed(sender, args) {

         alert('request failed ' + args.get_message() + '\n' + args.get_stackTrace());

}</script>

9. To update List

<script type="text/javascript">

var clientContext = null;

var web = null;

ExecuteOrDelayUntilScriptLoaded(Initialize, "sp.js");

function Initialize()

clientContext = new SP.ClientContext.get_current();

web = clientContext.get_web();

this.list = web.get_lists().getByTitle('My custom generic list');

list.set_description('My custom generic list description');

list.update();

clientContext.load(list, 'Description');

clientContext.executeQueryAsync(Function.createDelegate(this, this.onSiteLoadSuccess), Function.createDelegate(this, this.onQueryFailed));

function onSiteLoadSuccess(sender, args) {

         alert("list description : " + this.list.get_description());

function onQueryFailed(sender, args) {

         alert('request failed ' + args.get_message() + '\n' + args.get_stackTrace());

}</script>

10. To update ListItem

<script type="text/javascript">

var clientContext = null;

var web = null;

ExecuteOrDelayUntilScriptLoaded(Initialize, "sp.js");

function Initialize()

clientContext = new SP.ClientContext.get_current();

web = clientContext.get_web();

this.list = web.get_lists().getByTitle('My custom generic list');

this.oListItem = list.getItemById(1);

oListItem.set_item('Title', 'JK Updated');

oListItem.update();

clientContext.executeQueryAsync(Function.createDelegate(this, this.onUpdateListItemSuccess), Function.createDelegate(this, this.onQueryFailed));

function onUpdateListItemSuccess(sender, args) {

         alert("list item updated");

function onQueryFailed(sender, args) {

         alert('request failed ' + args.get_message() + '\n' + args.get_stackTrace());

}</script>

SharePoint 2010 : Client OM

2011-11-22T06:35:00.001-08:00

SharePoint 2010: Client OM

Introduction

SharePoint 2007 allows using its Server OM to run against server running SharePoint and to communicate from the client side allows using the Web Services. SharePoint Client OM designed to run from the Client OS where SharePoint is not installed.

SharePoint 2010 introduces three new client APIs which can be used to interact with SharePoint sites. The three APIs are targeted for three different types of clients:

1. NET Managed Client OM (for the applications like console, window, web etc ) which are not running inside SharePoint Context.

2. Silverlight Client OM. (For the Rich UI applications using the Silverlight)

3. ECMA Script (Jscript, JavaScript). This API is only available for applications hosted inside SharePoint (for example, web part deployed in SharePoint site can use this JavaScript API for accessing SharePoint from browser using JavaScript). Cross Page Scripting is not possible with the ECMA Script.

The new ECMAScript (JavaScript, Jscript), .NET managed, and Silverlight client object models each provide a subset of the server object model that is defined in Microsoft.SharePoint.dll, including objects that correspond to major objects at the site-collection level or lower in the SharePoint Foundation hierarchy.

The client object models are provided through proxy .js and managed .dll files, respectively, which can be referenced in custom applications like other object models. The object models are implemented as a Windows Communication Foundation (WCF) service (.../_vti_bin/client.svc), but uses Web bindings to implement efficient request batching. All operations are inherently asynchronous, and commands are serialized into XML and sent to the server in a single HTTP request. For every command, a corresponding server object model call is made, and the server returns a response to the client in compacted JavaScript Object Notation (or JSON) format, which the proxy parses and associates with appropriate objects.

SharePoint 2007 had no Client Object model available.

The main reason is that Microsoft has found lot of requests from SharePoint users to introduce more and more web services to get data out of SharePoint in the last couple of years. But introducing web services will not fix the issues, as Microsoft found, because then the request for more functionality in the web services will continue. Even if Microsoft provides a good numbers of web services with SharePoint, customization in web services will be required for different clients and this will make the out of the box web services unusable.

The following table shows the equivalent objects in Client and SharePoint Object Model.

The Site class represents site collections, and the Web class represents sites.

Sample Code :
ClientContext clientContext = new ClientContext (siteUrl);
Site siteCollection = clientContext.Site;
Web site = clientContext.Web;

How Client OM is developed and work under the hood?

It’s interesting how SharePoint team has developed the same set of classes for three different sets of applications (Managed, Silverlight and ECMAScript). There is same class ListItem for three different set of applications

Client Type	Assembly/File
Managed Client	Microsoft.SharePoint.Client
Silverlight	Microsoft.SharePoint.Client.Silverlight
ECMAScript	SP.js

To ensure the same class object (say ListItem) behaves similarly in three different types of applications SharePoint team followed the steps described below:

a) SharePoint team first set attributes to the SharePoint classes and methods and properties that need to be exposed in Client OM.

b) Then a code generator is run against the SharePoint object model to generate client OM automatically.

This automated code generation has ensured maximum compatibility between these three sets of APIs.

How the Client-Side Object Model Works

An application that uses SharePoint content interacts with the API in several ways—call methods and get the return values, pass a Collaborative Application Markup Language (CAML) query and get the results, and set or get properties. After you use the API to perform a specific task the SharePoint Foundation 2010 managed client object model bundles up these uses of the API into XML and sends it to the server that runs SharePoint Foundation. The server receives this request, and makes appropriate calls into the object model on the server, collects the responses, forms them into JavaScript Object Notation (JSON), and sends that JSON back to the SharePoint Foundation 2010 managed client object model. The client object model parses the JSON and presents the results to the application as .NET Framework objects (or JavaScript objects for JavaScript). The following diagram shows these interactions.

SharePoint 2010 Namespaces:

Microsoft.SharePoint.Client is the core namespace used for the .NET managed and Silverlight object models, and SP is the core namespace for the JavaScript object model.

In addition to the core namespace, SharePoint 2010 provides the following namespaces.

.NET Managed and Silverlight	JavaScript
Microsoft.SharePoint.Client.Application	N/A
N/A	SP.Application.UI
N/A	SP.Ribbon
N/A	SP.Ribbon.PageState
N/A	SP.Ribbon.TenantAdmin
N/A	SP.UI
N/A	SP.UI.ApplicationPages
Microsoft.SharePoint.Client.Utilities	SP.Utilities
Microsoft.SharePoint.Client.WebParts	SP.WebParts
Microsoft.SharePoint.Client.Workflow	SP.Workflow

The following table shows the equivalent objects that the new APIs provide for common SharePoint 2010 server objects.

Server	.NET Managed and Silverlight	JavaScript
Microsoft.SharePoint.SPContext	Microsoft.SharePoint.Client.ClientContext	SP.ClientContext
Microsoft.SharePoint.SPSite	Microsoft.SharePoint.Client.Site	SP.Site
Microsoft.SharePoint.SPWeb	Microsoft.SharePoint.Client.Web	SP.Web
Microsoft.SharePoint.SPList	Microsoft.SharePoint.Client.List	SP.List
Microsoft.SharePoint.SPListItem	Microsoft.SharePoint.Client.ListItem	SP.ListItem
Microsoft.SharePoint.SPField (including major derived classes)	Microsoft.SharePoint.Client.Field	SP.Field
Microsoft.SharePoint.WebPartPages.SPLimitedWebPartManager	Microsoft.SharePoint.Client.WebParts.LimitedWebPartManager	SP.WebParts.LimitedWebPartManager

The new client APIs do not provide administration objects or objects that are higher than site collection: SPSite class in the server object model.

Color Coding the Custom List Column with the Group By Column option in SP 2010

2011-11-19T02:46:00.001-08:00

You can follow the below link to generate the code and follow the instructions. The below blog gives more information about the OOTB concepts also.

Color Coding Calenders or lists

Main Problem :

When any list item is expanded ,it was not effected with the color coding (fig.1).

fig.1

But after expanding the second list item, the first list item was effected with color coding instead of current expanded list item.This behaviour will continue untill the last list item (fig.2,3,4).

fig.2

fig.3

Solution :

Go to the List Settings - > All Items View ( Current View Settings) - > Under Group By, In the By default show groupings : Select the Expanded (fig.4,5)

fig.4

Final Result :

fig.5