Skip to main content
Curator can allow users to save a Custom View of a Dashboard, which will include any applied filters and parameters, and then load it again at a later date.

​
Enable Custom Views

  1. Navigate to the backend of the system (e.g. http://curatorexample.com/backend).
  2. Log in if prompted.
  3. Click on the Settings > Curator > Portal Settings in the left-hand side navigation.
  4. Click on the “Features” tab at the top of the main page content.
  5. Click to switch on the “Custom Views” setting under the “Toolbar Buttons (Tableau Actions)” section and click the “Save” button.

​
Enable create/load a Custom View

  1. Navigate to the frontend of the system (e.g. http://curatorexample.com).
  2. Log in if prompted.
  3. Navigate to the desired Dashboard by using the navigation menu.
  4. Modify the filters, etc. as desired on the Dashboard.
  5. Click on the Custom Views icon at the top right portion of the screen. Normally this is displayed on the right side of the title bar in the Dashboard.
  6. Enter a name for the new Custom View in the text box and click the “Create” button.
  7. To load a different Custom View, select an existing view from the drop-down and click on the “Apply” button.
Custom Views can be shared via direct URL links, allowing users to access specific Custom Views without manually selecting them from the dropdown. This functionality works similar to Tableau’s native Custom View sharing capabilities.
  1. Load the desired Custom View URL — either by applying an existing Custom View using the steps above (steps 1-7), or by creating a new Custom View (the URL updates immediately when the view is saved).
  2. Copy the current URL from your browser’s address bar. The URL will automatically include the Custom View parameter.
  3. Share the URL with other users who have access to the Dashboard.

​
URL Parameter Format

Custom Views are accessed through the curator_custom_view URL parameter (or the legacy ::custom_view parameter for backward compatibility). For example:
When a Custom View is loaded, Curator automatically adds a Custom View ID parameter (cvi) to the URL:
The cvi (Custom View ID) URL parameter contains Tableau’s unique identifier (LUID) for the Custom View, which ensures the correct view is loaded even if multiple Custom Views share the same name. This parameter gets automatically added to the URL for troubleshooting purposes by Curator. If no Custom View ID is provided via URL load, the first Custom View by match on name is selected and its ID is added as the cvi parameter. If a URL contains both the Custom View name and ID parameters, the cvi parameter takes precedence to ensure the exact Custom View is loaded. This means you can safely share URLs that include both parameters without worrying about ambiguity.

​
Legacy URL Format

For backward compatibility, the legacy ::custom_view parameter is still supported:
However, new Custom View links will use the modern curator_custom_view parameter format.

​
Sharing Private Custom Views

Private Custom Views are only visible in the dropdown for the user who created them. However, similar to sharing a Custom View in Tableau anyone with access to the Dashboard can see a Custom View using the direct link outlined above.

​
Listing a User’s Custom Views

Curator has a Dashboard Custom Views listing page (/dashboard/:custom_views) that shows the signed-in user’s own Custom Views as tiles. Each tile opens its Dashboard with that Custom View applied. There are two supported ways to give users access to this list, and both require the “Custom Views” setting above to be switched on:
  • In the navigation: add a menu item with the “Tableau Custom Views” link type. It only needs a Title. See Menu Items for more information.
  • On a Page: add a Tiles element in the Page Builder and set its Content Selection to “Tableau Custom Views” to show the same tiles alongside your other content. See Tiles for more information.
Switching the “Custom Views” setting off hides the menu link and empties the tiles, but nothing is removed: both come back when the setting is switched on again.

​
Assigning a Custom View to a Dashboard

Separately from the end-user feature above, an administrator can bind a single Curator Dashboard to one specific Custom View. Everyone who opens that Dashboard then sees the Custom View instead of the workbook’s default view, without having to select anything themselves.
  1. Navigate to the backend of the system (e.g. http://curatorexample.com/backend) and log in if prompted.
  2. Navigate to Tableau > Dashboards and open the Dashboard you want to change.
  3. Directly below the Dashboard drop-down, set the Custom View drop-down to the view you want to display.
  4. Click on the “Save” button.
A few things to be aware of:
  • The Custom View drop-down only appears once the Tableau Server, Site, Project, Workbook and Dashboard drop-downs have all been filled out and the selected Dashboard has at least one Custom View on Tableau. When there are no Custom Views to choose from, the drop-down is hidden entirely.
  • Its options are read from your Tableau environment rather than stored in Curator, so a Custom View has to exist in Tableau before it can be assigned here.
  • Choosing None removes the assignment and returns the Dashboard to the workbook’s default view.

​
Troubleshooting

​
The Custom Views listing is empty

The Dashboard Custom Views listing page (/dashboard/:custom_views) reads each user’s saved Custom Views through the Tableau REST API on Tableau Cloud and Tableau Server 2022.4 or newer, and from Tableau Server’s repository database on older releases. If the listing shows “Found no content” for users on one of those older releases who do have Custom Views, Curator was most likely unable to connect to the repository. Open the listing while signed in to the backend: when the repository connection failed, Curator shows a warning banner above the tiles naming the affected Tableau Server (frontend-only users just see the empty listing). Then follow the Tableau Server Repository troubleshooting steps to check the repository settings on the Tableau connection and read the full error in the Event log.