Does anyone have an opinion on best practices for handling SSRS report parameter visibility for custom reports. I like to make my parameters visible so users can re-run the report from within the report viewer without having to close the report and go through the front end again; however, when done this way for any subsequent runs of the report the report parameters will not be inserted into gooesoft_request_parameter. I suppose I could look the the execution log table on the report server to get this data, but it would be preferable if all the data were in the same place.
Thanks,
Mike
Once the report viewer renders the report, it’s nearly out of Tessitura’s hands. The ReportViewer and SSRS are in control once the report is rendered. It’s really up to you if you want to use parameters in the Report Viewer. This is the only way at the moment that custom screens within the application can take parameters, for one.
One thing to watch is whether you want those report(s) to be schedulable in the Tessitura Report Server. If the visible parameters don’t have defaults set, the snapshot creation can fail.
=>Ryan Creps
@Tessitura Network
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Michael Zankowski Sent: Monday, August 25, 2014 2:51 PM To: Ryan Creps Subject: [Tessitura Technical Forum] SSRS Parameter Visibility Best Practice
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
That makes sense.
Thanks!