Blog Archives

SSRS – SQL Server Reporting Services Report Manager Tips and Tricks

In the last post, we saw SQL Server Reporting Services Tips and Tricks to Improve the End-User Experience. In this post, we will see few tips and tricks on SSRS Report Manager.

Report Manager is a pretty decent interface and offers the necessary functionality for managing reports. In this post, let’s take a look at few very less known uses/features of SSRS Report Manager. In this post, we will take a look at the following tips and tricks:

  • Customizing Report Manager Header/Title
  • Uploading Custom File Types to Report Manager
  • Enable My Reports Feature

To continue reading, catch the full article here: SQL Server Reporting Services Report Manager Tips and Tricks.

Related Articles:

Advertisements

Passing Parameters To Report Through URL in SQL Server Reporting Services (SSRS)

I was working on one of the requirements for a client where in the application owned by the client had a set of values in report column. The requirement was to make each of the values in that column a URL, on clicking this URL the value gets passed as a parameter to another report and the report is rendered without having to manually select/enter the parameter.
 
I had implemented a similar requirement in SSRS 2005 for one of the previous clients. In this current requirement which I am talking about the implementation was in SSRS 2008, which from this requirement standpoint does not make any difference.
 
I knew that we need to concatenate the value of the parameter to the URL of the report and this will do the job. So I took the report URL from the Report Manager and tried to concatenate the parameter but ended up in failure.
 
To resolve this I tried searching the web and found one article (http://www.mssqltips.com/tip.asp?tip=1336) which explained about various options/features which can be implemented through the report URL in SSRS.
 
While going through this post I found one very interesting thing and that is we need to concatenate the parameter value to the Report Server URL of the Report and not the Report Manager URL of the Report.
 
 
Many times we end up implementing the things in a straight forward fashion and hence dont come accross this kind of peculiar situations. However sometimes when we try doing the same thing differently, we end up meeting with this kind of peculiar findings which are worth treasuring in ones knowledge base.
 
Trying to implement something in different ways is worth it since we either end up finding an alternate/better/worst option which can be used to justify the best among the solutions identified or end up finding this kind of scenarios which have only one way to implement.
 
Happy Reporting 🙂