.rdlc reporting bound to Object Data Source in Three layer Application

1
votes

i have the following situation, i have a Reporting layer(stand alone) in asp.net application(NOT website, this means NO App_Code folder exists), and i want just to create Object Data Source to take an Object in a separate layer(lets say from Data Access Layer), and then to use that Object Data Source to create a report, i have spent my whole day working around that, tons of work around's and articles on the web, but does not mention what i really want to do, any answer is appriciated...

just to make things more clear here, assume the following:

i have a solution with the follwoing layers,

  • UI
  • Reporting(has NO Employees object) just a reference
  • Business Logic
  • Data Access Layer(Employees-->GetEmployees(),

all i need is as mentioned above, i want to create Object Data Source from Reporting layer, to take Employee object from DAL, and then use it's GetEmployees method to be added to report, i think its more clear now, since also Reporting layer has NO App_Code folder.

1
.netreportingrdlcobjectdatasource
Just curious if you've made any progress with this? I'd love hear what you did to accomplish this. - MattSlay
@MattSlay actually not much, it was annoying to have such an issue not solved until now, because i was in a hurry to know and to implement, at last all i did is using DataSet in the same Web.UI Layer - Saeedouv
It's a shame this question never got answered, this is exactly what I'm wanting to do. A very rare topic indeed, definitely a custom-rolled solution. - invert

1 Answers

0
votes

The way Ive been doing it is by creating a class that has a property of type List. I dhave a method called LoadReport(params......) in this class where I would call GetEmployess to populate my property.

I would then add a new Dataset in the report designer, selecting to bind to Object, and selecting the class i created. Once finished the dataset will allow you to expand the List property where you can drag different fields onto the designer.

Ive done this in VS2008, currently attempting in VS2010