views:

61

answers:

1

I have data that will be generated by users at runtime by performing queries. The shape of the data is unknown because users can choose which fields to bring back.

The application is an ASP.NET MVC web app. The data will be .NET POCOs. However, each object could have properties that are collections of other objects.

I want to use the RDLC format for the reports so that I can leverage the PDF, Excel, Word, etc export functionality.

I envisage the data being displayed in a grid, with nested grids for the collection properties.

  1. What are my options for generating the RDLC data?
  2. Can RDLC handle nested tables/grids for my collection properties requirement?
+1  A: 

I investigated this theme a year ago, searching for an object model to generate RDLs in memory. There wasn’t one, but there are rumors about. A quick investigation nowadays: An object model called RDLOM exists, but isn’t really supported by Microsoft.

My actual approach uses a self generated object model build upon RDLs scheme.

This is a less-than-ideal solution, because you need to know the generated object in detail and because the object creation code is really ugly. But the other workarounds I found in my investigation use XML or XSLT directly to generate the RDL and they are poor in their own way.

Dirk
Thanks for your answer. After struggling to get RDLCs to work for me I ditched it altogether and hand crafted code that generates PDFs using iTextSharp. I didn't like it at first as it _"didn't feel right"_, but it turned out to be much easier than mucking around with RDLCs.
GiddyUpHorsey