Monday, August 22, 2011

URL Parameters Utilized in Reporting Services



This article tells you probably the most common reporting parameters to implement in Microsoft SQL Server Reporting Services.

When get to the [http://reportserver/reportserver/foldername/reportname]

The last command inside url is & rs: Command=Render

You could add another commands the following:

& rc: Parameters=Collapsed

  • This collapses the parameter bar but sends the parameters inside the URL within the browser
  • & rc: Parameters=true

  • This shows the parameter bar which is the default
  • & rc: Parameters=false

  • This prevents the parameters from being passed during the browser and expanded
  • & rc: toolbar=false

  • This hides the toolbar
  • & rc: format=PDF

  • This will start the report as being a PDF
  • & rs: Format=EXCEL& rc: OmitFormulas=true

  • This will open the report in Excel
  • rs: ClearSession=true

  • This clears the session state for any user. Used the spot where the caching belonging to the report prevents the designer from seeing their updated report and/or data.


  • * It's a vital parameter to recognize fat loss often these days, the report data doesn't update immediately unless parameters are changed, and also your report may show cached data via a set. & rc: StyleSheet=MyCustomStyle

  • Note don’ t add the. css extension. Of which this style sheet are required to be within the folder Program FilesMicrosoft SQL ServerMSSQLReporting ServicesReportServerStyles folder.


  • Use the HTMLViewer. css because your base template.
  • ReportServer Parameters:

    If you add? /FolderName/ReportName as soon as the [http://servername/reportserver] you possibly can run the report.

    The same applies if you would like list the reports, then just type? /FolderName as soon as the [http://servername/reportserver].

    This happens to be used if the user merely has permissions along at the folder level, not the main level.

    Attachments:

    Disclaimer: This post is provided as it is. It is actually intended for a guide only and really should not relied on in production unless extensive testing has become done.

    .