Hello all,
Rather than re-invent the wheel, has anyone here ever tried persisting their report assemblies within a database?
The scenario is this; a hosted application environment where customers share the same database. Data is contextual based on the logged in customer. Nothing new here. However, every customer has different reporting requirements. I need an effective way of delivering only those reports that the are specific to the customer.
I don't want to build a giant assembly to contain every report for every customer. Instead, I would like to create customer specific report assemblies and then use them based on the customer logged in.
I know this can be accomplished using SQL Server Reporting Services - persisting RDL files to a database. Can something similar be accomplished using the Telerik Reporting?
No, creating a WCF RIA or web service, or similar, is not an option.
Any thoughts?
Cheers,
Paul
Rather than re-invent the wheel, has anyone here ever tried persisting their report assemblies within a database?
The scenario is this; a hosted application environment where customers share the same database. Data is contextual based on the logged in customer. Nothing new here. However, every customer has different reporting requirements. I need an effective way of delivering only those reports that the are specific to the customer.
I don't want to build a giant assembly to contain every report for every customer. Instead, I would like to create customer specific report assemblies and then use them based on the customer logged in.
I know this can be accomplished using SQL Server Reporting Services - persisting RDL files to a database. Can something similar be accomplished using the Telerik Reporting?
No, creating a WCF RIA or web service, or similar, is not an option.
Any thoughts?
Cheers,
Paul