This issue is just now arising for us because we have to meet
a new requirement of running in an Azure, load balanced environment. Instead of trying to move to that environment
with the obsolete ReportViewer, we decided the time to upgrade to the HTML5
ReportViewer was long overdue.
We have an accounting software application, which has 300+
existing reports/sub-reports, all of which were created with the Visual Studio
report designer, having the .cs extension. Essentially, we allow our customers to configure what they want to see
in a report. Based on what they
configure, we add individual reports to a ReportBook. This method works fine with the obsolete
ReportViewer. Now that we have upgraded
to the HTML5 ReportViewer, we are seeing these issues.
A specific example is our General Ledger’s Detail Ledger
report, where customers can select which funds in the account structure to
report on. Because each fund can have N number
of departments, which can also have N number of accounts, the report on one
fund can span several pages. For this type
of report, we put each fund’s report in a ReportBook, which allows the customer
to use the document map to quickly navigate between funds. Again, this method works fine with the
If I’m understanding you correctly, it seems that once any
ReportBook is generated, no other ReportBook can be generated until after the
previous one expires. This seems quite restrictive. I would think that because, as you say, a ReportBook
can have N number of reports in its collection, each generation of a ReportBook
might need to be considered unique.
I will be more than happy to work with anyone on your end to
come to a resolution for this, as moving to an Azure, load balanced environment
is a high priority for us.