Hi Clint,
The page with the viewer is not suitable as the HTML5 Viewer (including the HTML5 WebForms wrapper) is a client-side widget, where reports are resolved, processed and rendered on the server.
The HTML5 Viewer sends messages (string descriptions) what should happen on the server, and it is the Reporting REST service that reads the message, creates objects on the server and delivers content to the viewer. This is the reason to use a custom resolver for the Reporting REST service.
About the approach illustrated in http://www.telerik.com/support/kb/reporting/details/changing-the-connection-string-dynamically-according-to-runtime-data, the report is deserialized at run-time and the modified Telerik.Reporting.Report object exists only in memory. The TRDX file is not modified actually.
Regards,
Stef
Telerik by Progress
The page with the viewer is not suitable as the HTML5 Viewer (including the HTML5 WebForms wrapper) is a client-side widget, where reports are resolved, processed and rendered on the server.
The HTML5 Viewer sends messages (string descriptions) what should happen on the server, and it is the Reporting REST service that reads the message, creates objects on the server and delivers content to the viewer. This is the reason to use a custom resolver for the Reporting REST service.
About the approach illustrated in http://www.telerik.com/support/kb/reporting/details/changing-the-connection-string-dynamically-according-to-runtime-data, the report is deserialized at run-time and the modified Telerik.Reporting.Report object exists only in memory. The TRDX file is not modified actually.
Regards,
Stef
Telerik by Progress
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