When linking to reporting service reports either SQL or FetchXML (externally published). You can customise the user experience.

### No Toolbar

http://**ssrs.bsmt.uk**/reportserver?/ **SampleReports/Sales Order**&rs:Command=Render& **rs**:Format= **HTML4.0&rc:Toolbar=False**

### Straight to PDF

http://**ssrs.bsmt.uk**/reportserver?/ **SampleReports/Sales Order**&rs:Command=Render& **rs**:Format=PDF& **rc**:Toolbar=False& **CRM_Filtered_accountid=536**

### Common Parameters

Parameters are case-insensitive and begin with the parameter prefix rs: if directed to the report server and rc: if directed to an HTML Viewer.

**Server Name, ideally FQDN**  
**Folder on report server where the report is located**  
**Name of the report**

**Output (rs):**
- Web display
- HTML5
- HTML4.0
- ATOM
- MHTML
- Automatic Download
- PDF
- PPTX
- EXCEL
- WORD
- CSV (bug around table headings, shows field name not name, no spaces)
- IMAGE
- XML

**Display the toolbar (True or False), not applicable to non-web display (rc)**
**Pass a parameter value to the report (rc)**

**More information**  
[https://docs.microsoft.com/en-us/sql/reporting-services/url-access-parameter-reference?view=sql-server-2017#bkmk_reportserver](http://docs.microsoft.com/en-us/sql/reporting-services/url-access-parameter-reference?view=sql-server-2017#bkmk_reportserver)

### ADFS

When using ADFS on-premise and trying to preview reports in Visual Studio, do not put https:// on the front of the server connection name (URL).