Have the ability for reports to be generated at defined intervals and delivered to one or more defined destinations - together. For example, a monthly report pack (consisting of a number of reports) can be sent to a client with all reports attached to the single email or compressed into a single zip file, or merged into a single Excel workbook, or PDF file before delivery.

We are disappointed with the lack of SSRS improvements over the last 8 years.  We use data driven reports extensively.  For example, every day at 10am we run some report that emails everyone a list of items in their inbox from a custom application that routes them a task they need to act on.  

The problem we experience is that there is no way to flag an item as "emailed" successfully. So we end up either writing our queries to only select the previous 24 hours worth of data, or we write the select of the data inside an SP that also updates the data to mark them as "emailed" even though if there is a problem rendering the report or a problem contacting the email server, the emails won't actually go out.

Basically if we could have a data driven subscription, and while the server is looping through the data, sending off emailed reports, we could get a hook to update status for the item that was just emailed, or just errored during report rendering.

Hi,
   You guys give the tool,but not release it's value enough;Will there are a method to localize the desinger or compile the designer from source by myself?

Our company has many different profit and loss groups which act as mini-companies that share customers, vendors & transport companies. Each group doesn't want the other groups to view reports relating to their contracts, shipments & invoices.

This has been one of the failing of the Microsoft Report Server. I would have to pass in the query string the groupid. Any group could manipulate the query string to see other groups reports. So all reports are built in the web app with the groupid setup in their profile.

A solution to our type of business reporting needs would be helpful. Otherwise we will just roll our own reports in the next version also.

Following the ReportServerManual.pdf I meet the system requirements, using Visual Studio 2013 and have followed the installation guide but I am getting the following error when running the report server web application;

"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 50 - Local Database Runtime error occurred. Cannot create an automatic instance. See the Windows Application event log for error details.
)"

I have checked the application pool identity has permission to the files.
Please advise.  Kind regards, Scott.

In many cases one can't simply ask users to download an installed report builder. The reports should be buildable in a web based tool.

Much needed. :)

It would be great if users didn't need to authenticate with two different web applications.

I would use the report server integrated with my current ASP.net website. It would be great if it authenticated and authorized users based on the same roles also.