I've been working with SSRS 2005 reports for a little while now, and I've had a few requests come across asking for individual users to be able to save the parameters they use for the next time they run the report. Is this feasible? Is it a part of the "My Reports" role? Any thoughts?
I don't know if that can be done using the report manager, but you could always use URL parameters and pass through that way, then just give them the link to follow which will take them to their report (or render it as a PDF or other format if you wish) and already have the parameters passed in.
Here is a link that will take you to a lot of MSDN documentation about URL Access for your Reports.
I think you'll have to stop using the built-in UI and build your own report front-end to do that. I have always used RS this way and it is not all that complicated.
Related
I am interested in learning how to optimize my Action Property of an object in my SSRS Report.
All of the linked reports use the same Data Source. So, should I put the Data Source in the Shared folder and have all the report projects in the same solution?
The Action properties for the object have the options under "Enable as an action":
Go to report
Go to bookmark
Go to URL
The option for "Go to URL" works for the main report that is sent as an email alert subscription, but, as for the other reports that launch in a browser, I wonder if the option "go to report" will be a better choice? Would it be, and how would that be set?
Well, this answers part of my question:
The Go to report action is mostly used to go to a subreport, where you hand over a parameter or a value. If you dont pass any of these Go to URL would be the better choice.
How you handle your datasets depends on your setup. If your reports load fast and the datasets also, dont bother with shared datasets. Just load the same dataset again.
You can also insert a sever between your database and the report server which caches all the datasets. So you just load your dataset once in the morning and the reports use the cached one.
Does anyone know if it is possible to have SSRS log a PDF of every report run? I'd like to store the output (preferrably a PDF) somewhere of every report. I need to store what was visually presented to them, not just the parameters that were passed in.
Can SSRS do this out of the box somehow? If it can't, I'll have to log a copy via code on each call we make to the server, which I'm worried will slow down our application. Our reports are run from front-end code calling into SSRS, if that matters.
Thanks in advance for any help!
I don't think its possible out of box. Its a very unique requirement.
Possible solution is to create a report which will be using ReportServer.dbo.ExecutionLog table to generate report of execution. Once your report is ready you can configure it to generate PDFs. You can refer to http://blogs.wrox.com/article/creating-a-report-server-usage-report-with-sql-server-reporting-services/ for creating such report.
i have developed SSRS report with has summary report which is linked to six sub reports. i have provided eight parameters in summary report to make it user friendly. But when linked to sub reports it is working fine, but i want to provide back to summary button(link) in other sub reports.And it should be in a such a way that summary report should not be reset.(i.e Parameter selected should not change in summary report).
Any one has a solution for it.
Waiting for your positive response.
Thank you,
Adding buttons to the ReportViewer is a mind field at best. (Although, using the .NET web version, it's possible to add something like a "Clear/Reset Button" using JavaScript.)
However, the functionality you are after is already available, see the Microsoft Documentation on Configuring and Using the ReportViewer Toolbar.
I have created few SSRS reports in SQL server 2012 with Visual Studio 2010 version.
And I have deployed them to one SharePoint Site.
I want to make this automated, so that data available in the reports are up to date.
So, now I would like to create SSIS package which will run periodically to get up to date data using integration services. I am very much new to SSIS. I have tried to look at different sites for this, but I am not getting an exact idea from where to start.
Can anyone please guide me on this? How can I create a WSDL file URL for the SharePoint report? Do I really need it if report is already made in SSRS or do I just want to run that?
Thank you.
Would SSRS caching solve your problem?
Otherwise, there's nothing SSIS specific to solving your problem. You will simply need to use the .NET library to visit the page with the appropriate parameters. Visit your report page and copy the full URL.
Inside a Script Task use that URL as part of the WebClient. You'll probably need to supply credentials with this. No need to deal with storing the output, you'll simply want to validate that you get a 200 message code
Can you clarify what you are trying to achieve? Do you want to automate the running of the Reporting Services reports? In that case you should look at Report Subscriptions.
I need to create a report(rdl) in SQL reporting services 2008. In that I need to create in runtime. The report has chart. I will specify the type of chart, font, alignment and all those stuff in runtime.
Is there any option for using this in SSRS 2008.
An rdlc is just an xml file so you can manipulate it at runtime, it's not a trivial undertaking though. You can find the rdl spec at http://download.microsoft.com/download/6/5/7/6575f1c8-4607-48d2-941d-c69622e11c32/RDL_spec_08.pdf.
There's a downloadable example of creating an rdlc for a table and a matrix dynamically, as well as lots of other useful report viewer info at http://www.gotreportviewer.com/.
You can generate the RDL however you want, it is just an XML file. But you will only be able to run the report locally. To run on the server you would need to deploy the report first, as the server does not run the RDL files directly.
I suppose this is still possible, but it would be pretty slow, and the report would not appear in the report manager or anything before hand.
However, your probably making this problem more complicated than it needs to be. I have work on projects where we generated the RDL and deployed daily with a custom application, and it is almost always not worth it. There is usually a better way.
You can set almost all the parameters of the chart using expressions. The only thing that can't be set is the chart type, but there are ways to get around that as well. Like having all the chart types you need created on the page, but making all except the one you want visible.
Yes...
to do so, you will need to either have an existing rdl file to modify, or you need to completely generate it from code.
All the SSRS xml is stored in the database in a table called catalog. You'll have to use the GUID of that report to access it, or insert a new row creating a new report.
once you're done swapping out your report server xml, the report server will have a "new" report that you can then call via your web page, or via SSRS url parameters.
past that clean up the catalog table if you see the need to.
I'll be honest with you though, this is very far from best practice, best practice that I'm aware of would be to embed the data you need to display in your web page in the form of a widget.