Thank you for your effort and the time to post your solution for other community members.
We just want to recommend you to use expressions instead of events:
The bonus of the Expression engine is it will validate internally the given data before processing it. Also data manipulation to be separated in its own Data Access Layer, and leave the report to communicate with the DAL. All operations for data retrieval can be placed in the DAL and controlled from outside with parameters mapped to report parameters. This approach is preferable with complex reports as issues sources are easily tracked between layers and the maintenance of reports on upgrade is reduced to updating references and checking the report designer.
Also we have some considerations about working with events
as that you need to work with processing items instead of their definitions. For example check the Using Report Events
We updated your Telerik points to thank you once again. We will be glad to see more posts from you.
New HTML5/JS REPORT VIEWER with MOBILE AND TOUCH SUPPORT available in Telerik Reporting Q3 2013! Get the new Reporting version from your account or download a trial.