Support custom assemblies or at least offer some alternative
Custom assemblies in SSRS 2008 are a great way to re-use code in different reports. They are also unit testable.
Right now there seems to be no way to achieve this in SQL Azure Reporting, so it looks like we'll have to copy-and-paste a lot of re-occurring visual basic functions from one report to the other. This makes building the reports more a more tedious and error-prone process, not to mention the lack of unit testing for custom functions.
3 comments
-
André van de Graaf
commented
To implement Translation and localization of reports it is essential to use assemblies in your SSRS reports, Like you can do in on premise SSRS reports. http://msdn.microsoft.com/en-us/library/ms159238.aspx#External We have one set of files with all translations which we want to use in all reports for multiple databases. Beside translations, the user should be able to see reports in his preferred localization. For instance thousand separator, number format etc.
-
SAVERIO COPPOLA
commented
SQL ASzure reporting it will guide you where yo opt to be and the toos of you know how. This Saverio always ready to gain a little more knolage to be used for the weel-being of the world ans so we shall.
-
Bill Voltmer
commented
I would settle for cutting-and-pasting VB functions between reports but I found that reports with code won't run at all on SQL Azure Reporting due to RDLSandboxing. Perhaps webservice calls are preferred?