KNOWLEDGE BASE

Unable to Use Parameters as URL Parameters to Filter a View


Published: 19 Jun 2013
Last Modified Date: 07 Feb 2017

Issue

When working with views that are filtered on parameter, passing this parameter as a URL parameter does not filter the view.

Environment

Tableau Desktop

Resolution

The below example uses Superstore sample data and filters a workbook by "Category" across all worksheets using parameters: 
  1. Right-click in the Data window and then select Create Parameter
  2. In the Create Parameter dialog box, do the following, and then click OK: 
    • Name the parameter. In this example, the parameter is named CategorySelect
    • For Data Type, select String
    • For Allowable values, select List
    • For List of Values, enter All, Technology, Furniture, Office Supplies
  3. Select Analysis > Create Calculated Field
  4. In the Calculated Field dialog box, do the following and then click OK: 
    • Name the calculated field. In this example, the calculated field is named Matches Parameter. 
    • In the formula field, enter a calculation similar to the following: [CategorySelect]="All" OR [CategorySelect]=[Category] 
  5. Drag the newly created calculated field from the Dimensions pane to the Filter shelf. 
  6. In the Filter dialog box, select True, and then click OK. 
  7. On Filters, right-click Matches Parameter, and then select Apply to Worksheets > All Using This Data Source
  8. Publish the workbook to Tableau Server.
  9. The published view can now be filtered with the parameter as a URL parameter as follows: http://<servername>/#/views/<workbook>/<sheet>?param1=value1,value2&param2=value 
Note: URL parameters are passed only to a specified view (<sheet>) of a specified workbook (<workbook>). Where: 
  • <workbook> = Superstore 
  • <sheet> = Performance 
  • ?param1 = Category 
  • value1 = Furniture 
For example: http://<servername>/#/views/Superstore/Performance?Category=Furniture 

Cause

For more information about URL parameters, including screenshots demonstrating the URL patterns; see How View URLs Are Structured
Did this article resolve the issue?