URL Access (SSRS)
URL access of the report server in SQL Server Reporting Services (SSRS) enables you to send commands to a report server through a URL request. For example, you can customize the rendering of a report on a native mode report server or in a SharePoint library. You may have viewed the report using a specific set of report parameter values, or you may have been viewing a particular page of interest in the report. You can encapsulate this information in the URL using predefined URL access parameters. You can further customize how the report server processes the report by embedding parameters for rendering formats or for the look and feel of the report viewer. You can then paste this URL directly into an email or Web page to let others to access your report in the same manner in the browser.
Other actions you can perform through URL access are:
Send commands to the HTML viewer, such as adjusting its look and feel
List the children of a catalog folder
Retrieve the XML definition of a catalog item
Render a specific report history snapshot
Manage report sessions
For the complete list of commands and settings available through URL access, see URL Access Parameter Reference.
URL requests to the report server contain parameters that are processed by the report server. The way in which the report server handles URL requests depends on the parameters, parameter prefixes, and types of items that are included in the URL. Report server URLs adhere to the URL formatting guidelines as proposed by the joint World Wide Web Consortium W3C/IETF draft standard. Reporting Services URL functionality is compatible with most Internet browsers or applications that support standard URL addressing.
URL requests can contain multiple parameters that are listed in any order. Parameters are separated by an ampersand (&) and name/value pairs are separated by an equal sign (=).
The Web service URL of the report server. For native mode, it is the Web service URL of the report server instance configured in Reporting Services Configuration Manager (see Configure Report Server URLs (SSRS Configuration Manager)). For example:
For SharePoint integrated mode, it is the URL of the Reporting Services proxy at a SharePoint site integrated with Reporting Services. For example:
It is important the URL include the _vti_bin proxy syntax to route the request through SharePoint and the Reporting Services HTTP proxy. The proxy adds some context to the HTTP request, context that is required to ensure proper execution of the report for SharePoint mode report servers.
The relative path name of the item in the native mode report server database, or the fully qualified URL of the item in a SharePoint catalog.
The path of the catalog item. For native mode, it is the relative path of the item in the report server database, beginning with a slash (/). For example:
For SharePoint integrated mode, it is the fully qualified URL of the item in the SharePoint library, including the item extension. For example:
Used to separate name and value pairs of URL access parameters.
Optional. A prefix for the URL access parameter (for example, rs: or rc:) that accesses a specific process running within the report server.
If a prefix for a URL access parameter is not included, the parameter is processed by the report server as a report parameter. Report parameters do not use a parameter prefix and are case-sensitive.
The parameter name.
URL text corresponding to the value of the parameter being used.
Access report server items, such as reports, shared data sources, and resources.
Pass report parameters to a report.
Set the locale of the report parameters in the URL access string, which defines the locale-specific interpretations of dates, currencies, and so on.
Send rendering extension specific settings that customize how the report is rendered.
Export a report directly to a file format without viewing it in the browser.
Open a report and navigate directly to the location of a string.
Render a specific report history snapshot.