We have a client/server solution, and our client software is Winforms. Our client-side does not have access to the database server, but it communicates to our server through our own home-rolled rpc services (ip and/or http communication).
We have a partially implemented solution where our server software runs the sql and sends it back to the client as a datatable, along with the Telerik report definition. Our client software puts these two pieces together, and displays the resulting Telerik report in a ReportViewer.
This works fine, except we want to utilize Telerik reports where report parameter tokens are embedded into the sql statements, e.g. "SELECT * FROM TableA WHERE FieldA = @parameterA". This does not work with our current solution, as our server does not have the parameter values to inject into the sql, because at that point, the ReportViewer on the client side has not yet allowed the user to select parameter values.
What approach would you recommend to resolve this? Continue with our solution and somehow send the user's parameter values to the server before the ReportViewer attempts to display the report (i.e. right as the user clicks the "Preview" button)? It seems like we are re-inventing the wheel.
Or use Telerik Reporting Services (REST or WCF), and scrap our current approach? I'm not sure I know what flavour of Telerik Reporting Services would be most appropriate in our situation, or if is the proper approach at all.
Thanks,
Eric.
We have a partially implemented solution where our server software runs the sql and sends it back to the client as a datatable, along with the Telerik report definition. Our client software puts these two pieces together, and displays the resulting Telerik report in a ReportViewer.
This works fine, except we want to utilize Telerik reports where report parameter tokens are embedded into the sql statements, e.g. "SELECT * FROM TableA WHERE FieldA = @parameterA". This does not work with our current solution, as our server does not have the parameter values to inject into the sql, because at that point, the ReportViewer on the client side has not yet allowed the user to select parameter values.
What approach would you recommend to resolve this? Continue with our solution and somehow send the user's parameter values to the server before the ReportViewer attempts to display the report (i.e. right as the user clicks the "Preview" button)? It seems like we are re-inventing the wheel.
Or use Telerik Reporting Services (REST or WCF), and scrap our current approach? I'm not sure I know what flavour of Telerik Reporting Services would be most appropriate in our situation, or if is the proper approach at all.
Thanks,
Eric.
1 Answer, 1 is accepted
0
Hi ,
With the current approach you can serve the desktop client with the whole set of data and apply the filter via report parameter in the report.
If you want to limit the data on retrieval, you can use a data service or other and consume it in code, where the method in which data is retrieved can be wrapped by an ObjectDataSource component. The data retrieval can be controlled via report parameters mapped to the underlying method's parameters as in the Using Parameters with the ObjectDataSource Component article.
Consider the example in the Connecting Telerik Reporting to OData feeds blog post.
Let us know if you have any further questions.
Regards,
Stef
Telerik
With the current approach you can serve the desktop client with the whole set of data and apply the filter via report parameter in the report.
If you want to limit the data on retrieval, you can use a data service or other and consume it in code, where the method in which data is retrieved can be wrapped by an ObjectDataSource component. The data retrieval can be controlled via report parameters mapped to the underlying method's parameters as in the Using Parameters with the ObjectDataSource Component article.
Consider the example in the Connecting Telerik Reporting to OData feeds blog post.
Let us know if you have any further questions.
Regards,
Stef
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.