My Top 10 RS Wish List
In the spirit of the season, I compiled a list of the top 10 things that I would love Santa to implement in the next release of Reporting Services (although it may look like this won’t happen next year :-). I purposely excluded enhancements to the RS data regions since it should be relatively easily to compile a list of the feature most folks complain about in the public ng.
- Exposing the intrinsic RDL object model to manipulate data regions and items programmatically. It will be great if this works similar to the ASP.NET user controls where controls can be added, changed, or removed at runtime. For example, custom code should be able to reference a table region to add, remove, and bind columns at runtime.
- Server-side events, e.g. OnReportRender, OnBodyRender, OnPrint, OnRegionRender, etc.
- A supported way to maintain state in custom code.
- Exposing the report datasets to custom code to allow programmatic navigation and data retrieval, e.g. looping through the dataset rows.
- Decoupling the Report Builder Designer and exposing it as a reusable .NET control which can be embedded in applications. Ideally, a developer should be able to pass the semantic model (or metadata described in a different format) the designer. The output of the WYSWIG manipulation should be returned in the form of RDL.
- Enhancing the Report Builder Designer to support custom code and plugging in custom function libraries.
- Simplifying CAS security to the three levels supported by SQL Server and SSAS – Safe, External Access, and Unsafe.
- Binding server-side reports to ADO.NET datasets.
- A conditional page break.
- The XML extension should support XML schemas and cast the column types to data types according to the schema.
Please feel free to add to the list and happy holidays!
