Was wondering if there is any way to get back into the Report Wizard in SSRS, after completing it. I find myself often wanting to tweak something, but can't see any way to get back into it without restarting everything from scratch - very annoying! Does anyone know a way?
Thanks
Unfortunately, I don't think it is possible to get back to the wizard without making a new report.
Related
I have a problem with my paginated report and I need help. I have three parameters in my design and whenever I run it, the parameters don't ever appear on the reports. I have tried it in different ways but the result always comes back to me same way. Please could anyone help me with this? Even when I click the parameter pane, the parameters are nowhere to be found.
I have also deleted it several times but still does not work.
Do you just try to run it on the preview mode? if so you just need to close the SSDT and reopen it
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
I can't figure out what is going on with my report in Access 2010. When I run it, all the queries and recordsources are generated and the report shows up, perfectly full of data and formatted in print preview. If I try and print a hard copy or export to PDF, the subreports don't print. I have done compact and repair, closed and opened, and check everything I know, but it's not working. The only thing that I can think of is that the subreports are based on temp tables I generate and set within VBA after I pull all the parameters I need. But I don't see why this would cause it to preview but not print? Any help would be greatly appreciated!!
Here's the solution I found... when I moved the table creation code to the button that prompted the report rather than having it use the openargs in the open event of the subreport, it worked. Don't know why exactly it liked it one place better than the other, but I'm glad that it works now!
After many hours in research and experimentation the only solution was a third party print function: http://www.lebans.com/reporttopdf.htm. Leben’s function always produces a printable PDF with visible subreports.
No modification of the report’s properties was of any value, though this is suggested by various posts; it failed to work for me. Similarly, compact and repair failed to help, as did the creation of a wholly new MDB file and importing all the forms/tables/queries. I ran the MDB in Access 2003 and in Access 2010 on another machine and had the same failure.
This points of course to the issue being embedded within Access. Research shows this has been an issue plaguing Access for many years; in its inimitable lack of care for users getting work done Microsoft has failed to even comment on this, much less fix it.
I had a similar issue and thought that I should post my fix in case someone else runs into the same problem.
I had a report with two subreports on it. From a form, I would select from several combo boxes and then hit the button to run the report. When the report opened (in preview and in report-view) it looked fine, and the subreports worked fine. However, when I tried to print or save, the subreports would not show up.
My solution was in my queries and in the form. The report's source queries were pulling criteria from the combo boxes on the form. Once the report was run, the combo boxes would clear, thus clearing the criteria for the queries. After the report is run, the report looks at the queries again when you try to print/save.
If you have a similar setup, I would suggest checking your source queries again after the report is run to see if you are still getting results. You should see the same data in your queries and in your report. If not, there's where to start looking. Hope this helps anyone else struggling with the same issue.
I am building a report with one "go to report" and in that new report I have one subreport. Now, when I´m sitting and working with the report and for instance changing the format for a cell the report doesn´t view the new changes directly. Sometimes it does. Sometimes I have to wait a while, sometimes I restart BIDS. Has anyone experienced this problem before?
I think the way VS maintains subreport data when designing means the definitions can get stale; does a Rebuild Solution before previewing help?
This should hopefully make sure everything is up to date and for a Report project/solution it should be quick to rebuild.
I have report with some messages, and I would like to know is there a way for RS to have checkbox or link which will, when clicked mark message as read, or in other words, inserts/updates isRead column for that id?
Is this even possible?
Is it possible? Yes. Is it easy? Not a easy as most things in SSRS. Will it be elegant? Probably not.
You could create a check box icon which would link back to the report or some other action on the server. This would need to be set to handle a parameter indicating the checkbox clicked. Build a stored proc or other mechanism in the report to catch these clicks and make your column changes.
The biggest problem with this approach would be that, by default, the entire report would need to rerun and reload. You might be able to get something working that keep this smaller, but I'm not sure how.
My advice: don't do it. SSRS isn't designed to support this sort of interactivity with the data source. You'll be fighting against the tool. Look for another interface for this.