Reporting Services: RSViewerPage

The main file used for displaying reports is the RSViewerPage.aspx. This page contains a breadcrumb and a webpart called ReportViewerWebPart. This webpart renders a toolbar, the report and a parameters pane.

Hide buttons from the toolbar

I saw a couple of articles of people who disable some toolbar buttons by diving into the ConfigurationInfo table of the Reporting Services Database. This method will work for a few buttons, but not for all of them. I discovered that you don’t need to adjust that database table at all. You can use the ToolBarItemsDisplayMode property of the ReportViewer WebPart. This property allows you to hide/show specific parts of the ReportViewer’s toolbar. Be aware, this property is an enumeration field.

For example: ToolBarItemsDisplayMode=’223’ will hide:

• Open with Report Builder (Action Menu)
• Subscribe (Action Menu)
• Atom icon

Before:

After:

Why 223? You have to make the sum of the values of the parts you want to include in the toolbar. The values are shown in the reference table below:

You can set the property by adding the property in the RSViewerPage.aspx like

<RSWP:ReportViewerWebPart id="m_sqlRsWebPart" runat="server" SuppressWebPartChrome="true" Height="100%" ToolBarItemsDisplayMode="223" Width="100%" />

OR

You can pass the property as a querystring rv:ToolBarItemsDisplayMode=”223”

Related posts:

• Passing URL report parameters to Reports in SharePoint Document Library in SSRS 2008 & R2
• Reporting Services ... Customizing the RSViewerPage.aspx Page
• Customize Actions on the RSViewerPage.aspx

Ogone – Feedback Parameters

The merchant can send some extra parameters in the hidden fields of the order form, in order to retrieve them as feedback parameters after the payment.

One of the hidden fields is the PARAMPLUS parameter. This field submits some parameters and their values you would like returned in the feedback request (as a querystring).

Be careful when you generate your SHA-OUT hash based on the incoming feedback parameters. You have to exclude all the extra parameters, you sent with the PARAMPLUS parameter, before generating the hash.

SharePoint Designer 2010 Action: Start Approval Process

The “start approval process” is a brand new workflow activity available in SPS 2010.

The Start Approval Process action behaves like a pre-built workflow—the logic is already defined in the action. The action has several different phases built into it that defines task behaviors, task process behaviors, logging to the History Log, e-mail notifications, and completion conditions. Although the action comes with pre-built logic, it still needs information from you—such as the users (the reviewers), the order in which the tasks are to be routed to the participants—serial or parallel, the default is serial, and the due dates for task completion.

You can customize the predefined logic within the activity by clicking on the ‘approval hyperlink’ (as shown below).

A quick example:

The out-of-the-box approval workflow includes the following settings in his association form: End on first rejection & End on document change.

As far as I know, you can’t set these settings by default in this activity. If you want to apply this behavior to your own build workflow you can, for example, customize your initiation / association form with two extra checkboxes and pass the values to the workflow or you just can remove the condition so that they’re ‘checked’ by default. The screenshots below give you an idea of how to (remove the ‘if clauses’ way) enable this behavior.

You can find the behavior of the End on first rejection in the ‘change the behavior of a single task’ section.

First, move up the logic within the condition. Then you can remove the condition.

You can find the behavior of the End on document change in the ‘change the behavior of the overall task process’ section.

First, move up the logic within the condition. Then you can remove the condition.

That’s it.

Slidedecks BIWUG on SPS2010 WCM and FAST Search 2010 available

You can find them here.

Getting started with the Client Object Model in SP 2010

Some useful resources to get started the with the Client OM...

• Using the SharePoint 2010 Client Object Model - Part 1
• Using the SharePoint 2010 Client Object Model - Part 2
• Using the SharePoint 2010 Client Object Model - Part 3
• Using the SharePoint 2010 Client Object Model - Part 4
• Using the SharePoint 2010 Client Object Model - Part 5
• Using the SharePoint 2010 Client Object Model - Part 6

• Zimmergren Part 1
• Zimmergren Part 2

How To: exclude welcome pages in search results

Remember there was a ‘welcome page search retrieval’ issue in SP 2007? If not… take a look at http://svengillis.blogspot.com/2009/02/no-searchresults-for-content-available.html

Fortunately, this issue has been fixed in SP 2010. In some cases, you still want to exclude welcome pages in the search results – just like in the old days.

To do this - follow the steps below:

• Navigate to the Search Service Application
• Make sure you did a full crawl on your content source
• Create a new rule in your search scope (all sites or whatever) as follow:
  
  
  
  By creating this rule you’ll eliminate the site URL (eg. /news) items. At this moment, the site default page URL is still included (/news/pages/default.aspx). In the next step we are going to eliminate them too…
• Create a new Crawl Rule
  
  
• Make sure you’ll do a full crawl again and that the Search Scopes are updated
• Notice that no welcome pages are found in the search results

Compare SharePoint Editions

A quick reference to compare SharePoint 2010 Editions (Foundation, Standard, Enterprise)