Skip to main content


Microsoft Sql Server Reporting Services (SSRS) is mostly pretty good. The report designer is ok, the flexibility you get with web services and the ASP.NET ReportViewer component is pretty good. If you're already running Sql Server then SSRS pretty much comes for free.

One aspect of SSRS that isn't too good however, is the default interface for running the reports. Officially known as 'Report Manager', but more commonly known as 'that thing you run reports with', it has a lot of shortcomings.

It was designed in the pre-ajax days, so although it does the job, it can be pretty clunky. It particularly struggles with reports that have lots of parameters, or reports that have multi-picks with a large number of options.

Given that SSRS is quite openly designed - most of the services are exposed through web services, and the ReportViewer component can be used to embed SSRS reports in applications - I would have thought there would be some good competitors to Report Manager out there. General purpose SSRS interfaces that are a bit more up to date. But as far as I could tell, as of last year, there wasn't.

So here's one that I have developed. Its called CrissCross, and it is an open-source ASP.NET application that provides an alternative front-end for running SSRS Reports.

You can download it from GitHub.

The key features are:

  • Nice clean jQuery/ajax interface for choosing reports and choosing parameters
  • For reports with lots of optional parameters, users choose which ones they want to use (instead of all parameters being displayed by default)
  • Better support for multi-pick parameters using Eric Hynds' jQuery UI MultiSelect Widget, which allows filtering within the multi-pick
  • CrissCross allows you to retrieve parameter choices you have used in previous runs of the report by pulling the data from the SSRS report log
  • Simplified home page shows the user the report they run most often, and the reports they have run most recently
  • CrissCross is open-source so you can take it and modify it to meet your needs
For more details, see the documentation and screenshots on Github.

(edit: changed old codeplex links to github)


Popular posts from this blog

Copying data to Salesforce Sandboxes using TalenD

A common problem with Salesforce Developer Sandboxes is that they are blank. Really you're going to want some data in there, so there are various strategies for copying data from your live instance to the Sandbox. There are some paid-for solutions - SFXOrgData , Salesforce Partial Data Sandboxes - but if you've got a decent ETL tool you can build your own. There are a bunch of free ETL tools for Salesforce: JitterBit Data Loader is good for quick ad-hoc tasks but the free version makes it difficult to manage specific ETL projects or share projects with other users Pentaho Community Edition - an open source edition of the enterprise version Apatar was a free open source Salesforce ETL which still works but development seems to have stopped since 2011 TalenD Open Studio is an open source ETL tool For the task of copying data from live to a Sandbox, either Pentaho or TalenD Open Studio could be used, depending on preference. Here's a good comparison of the dif

SSRS multi-value parameters with less fail

SSRS supports multi-value parameters, which is nice, but there are a few issues with them. This is how I deal with them. Two of the problems with SSRS multi-value parameters are: You have to jump through a few hoops to get them to work with stored procedures The (Select All) option, as shown above The reason the (Select All) option is a problem is that it is a really inelegant way of saying 'this parameter does not matter to me'. If you have a list with hundreds of values, passing all of them as a default option just seems wrong. Also, if your report shows the user which items they selected, printing the whole list when they choose (Select All) is excessive. So in this post I'm going to show my particular way of: Jumping through the hoops to get Multi-Value params in a stored procedure Adding a single '--All--' value that the report interprets as meaning all the options. Getting Multi-Value params to work with Stored Procedures This is

Remote Desktop on High DPI screens

Scott Hanselman wrote a nice blog post back in January about some of the issues you might face running Windows on a High DPI screen like that of a Surface Pro or Lenova Yoga. I'm kindof mystified that he didn't mention Remote Desktop though because thats been the number one problem for me on High DPI screens. That said, if you remote into very recent Server OS's like Windows Server 2012 R2, then apparently Remote Desktop will sort out the DPI scaling automatically. Perhaps Scott hadn't noticed the Remote Desktop issue because he only remotes into Server 2012 R2. Certainly if I was Scott, I wouldn't remote into anything less than that. But, in practice, I regularly have to remote into Server 2008 machines and yes even Server 2003. If you do that from a high DPI screen, the remote desktop is rendered at regular pixel size, which makes everything tiny. Its hard to show screenshots of High DPI screens that correctly convey the pixel size, so I've photoshoppe