In general, the purpose of the ObjectDataSource component is to provide data to the report in a declarative manner. The ObjectDataSource.DataSource should be the assembly qualified name or Type of the data access layer (class), where the reporting engine will use System.Reflection to create the instance of the class (by using its default constructor) and to execute its method specified by the ObjectDataSource.DataMember.
In order the ObjectDataSource Wizard to discover types, the project must be built and types must be accessible. It is recommended to have separate projects for data access layer, UI and reports.
If you are going to use the HTML5 MVC Viewer, please note that data objects are not transferred by the client to the server (the viewer does not use MVC model). The viewer submits short string formatted requests what resources to be prepared and rendered on the server, and then delivered by the Reporting REST service.
Thus data models used by views cannot be used directly by reports. Instead you can save data on the server and then access it on requesting a report (via data source component
On a side note, if you are using the Standalone Report Designer
, the ObjectDataSource component can be used with external assemblies extending the designer's functionality - Extending Report Designer
In order to provide you more accurate suggestions, please elaborate on the issue with screenshots and examples of the data access layer you want to use.
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items