is it possible to do a lookup in SSRS 2008 report from a Subreport? if so, can someone tell me how please?
No, the lookup function won't go beyond the scope of the report. Your question isn't very clear on what exactly you're trying to accomplish (which would be helpful) but I'll try to guess.
If you're looking to pass some values to the subreport from the parent's dataset you could check this blog post about doing that, though I haven't tried it myself. You could also use a shared dataset to avoid rewriting your queries if you need to use the dataset again in both of the reports.
According to this msdn social thread it doesn't appear to be possible to pass a value to the parent report from the subreport. However, another thread on sqlservercentral.com seems to have some promise but it didn't seem to work for everyone. Once again, I haven't tried it myself.
Good luck, and let us know if anything works!
Related
I have many reports which use a set of the same report variables:
Is there any possibility not to insert them each time manually when creating a new report? Or may be there is a possibility to share these variables between reports as , for instance, DataSources?
Can be used for this purpose assemblies?
Based on your question it's seems you're looking for a subreport. Sub Report is a tool available in the toolbox in SSRS. It allows you to create a report that can in included in all your other reports without have to rebuild the structure.
Once you've created your report in the sub report properties just specify the report and include the parameters used for the report (if any) see below:
If that's not what you looking for, then maybe it's shared data sets you're looking for.
Let me know if it's something completely different and I may be able to provide alternative solutions.
Thanks
Gav
I'm trying to figure out how (if it is even possible) to allow a user to add a 'flag' to say when they have actioned a row in an SSRS report. This would need to carry back into the underlying tables.
Any help is appreciated; whether it is telling me this is impossible or giving me an idea of where to start.
No, this is not possible in Reporting Services. You will need to look into building your own solution in .NET
Assuming a fairly conventional SSRS 2012 report (in Visual Studio 2012) with a main report, a set of sub-reports, a shared dataset that is populated at the start of the report, and a shared datasource.
Is there any simple way within a sub-report's custom code (this is VBA, right?) to access the shared dataset, either to read or update records locally? (No updates back to the database itself.) I'm seeing hints out there that this is possible but no clear examples yet.
And if the above is possible, assuming that a call in the sub-report changed a record in the shared dataset, could that record change be displayed in the main report body?
Yes and No.
I think the overall concept would work but a few points won't.
I don't think you'd be able to use the report dataset with VBA. The code won't have access to the report's datasource directly. You'd probably need to use ADO to access the db from VB.
The only way to see the updated data would be to refresh the report - either manually or automatically on the timer.
I don't see how the subreport is going to figure out what to update the value to. You might have some idea that I'm not seeing right now.
The easier way I see this working would be to use parameters that default to NULL. Then select the row to update with one parameter and the value with another. Then have an UPDATE in your main query that only runs if your parameters are populated.
When a user hits my report I require they select a parameter to continue. What I would like to do is explain to the user, before they have selected an option, a little about the parameter options. It is fairly straight forward in the report below, however I have others that are much more complex.
Currently, the user has to select options then view the report; at which time an explanation of the parameters is available as part of the report. To me, it seems silly that a user would have to pick something 'blindly' just to get an understanding of how that parameter will impact the results.
I realize that appropriate parameter naming goes a long way, and we do our best to make that happen. We have a few situations where a sentence or two would go a long way in clarifying something before a user runs a report.
I have also used default parameters in the past to get the report to fully load when they first hit the page but that is not the solution I am looking for here.
Thanks in advance for your help!
Not possible to do via any provided functionality. The only way you're going to get this is if you use custom CSS sheets when accessing the report (either as a URL querystring parameter, or replacing the default stylesheets), or otherwise creating your own report page(s) to house your reports instead of Report Manager.
This is in SSRS 2008.
I've created a report with a tablix, embedded in the tablix there is a subreport. This subreport contains a lot of information (and I mean a lot – it takes more than 45 sec to load it).
I don’t want to show it, or to be more precise – to process/load the data when the report initially runs. Note that I dont want to just not display it - because then all the data is still processed at initial load time.
Instead, I only want the subreport to be processed (and the data pulled down), individually, when I display it (e.g. clicking a + sign to toggle it, or any other option such as clicking an image/ link, while staying in the same report). I also don’t want to open the subreport in a different tab or something like that....
Does anyone know a solution? Maybe there is an onLoad method, dynamic subreport or something like that?
I tried looking into the DataElementOutput attribute, but that's readOnly... anything else?
Before you jump through a lot of hoops to implement a workaround, have you analyzed the execution plan for the query which is delivers the data for the subreport? If you haven't, it's worth it to see if performance can be improved by adding a covering index which will help the query optimizer to deliver the data quickly.
Hope this helps,
Bill
So, as it turns out, the problem was in fact because I had the subreport repeated for each row in the parent report. Thus, the subreport was called numerous times...
And according to MS, there is no way to dynamically process individual subreports. Had to solve this issue by splitting out the subreport (at least the data-heavy parts) to a seperate page. :(