Hi Al,
Based on you description, the only missing step is to add a connection string entry in the web application's web.config file. The connection string entry must have the name of the connection string used in the report.
On
configuring a SqlDataSource component you can save a connection string by name (it will be searched in the application's configuration file), or you can hard-code the connection string (it will be the same always).
If you have a scenario where the connection string should be changed at run-time, you can switch to an
ObjectDataSouce component that allows you to use a custom data retrieval logic. The data access layer can be loaded in the Standalone Report Designer tool by extending the tool's configuration -
Extending Report Designer (tutorials at the bottom).
About using the HTML5 Viewer, please check how it works in the
overview help article. In your case you are using the HTML5 WebForms ReportViewer, which is a wrapper of the original JS/CSS/HTML widget. The wrapper renders in browser the Javascript object and registers some scripts at the end of the page (please consider this if you will Ajaxify the page).
The
viewer's properties can be configured from the VS Property grid, where the VS item template provides the viewer with some default settings.
Regards,
Stef
Telerik
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?
Explore the
Telerik Feedback Portal
and vote to affect the priority of the items