Dashboard Views

Dashboard Views eliminate the need to manually adjust filters every time users need to view a dashboard’s data in a new context, allowing them to quickly access and reuse previously saved filter conditions across your dashboards.

Dashboard Views can be installed by an Admin, following the directions in Installing QBeeQ Plugins.

Operating system and version support:

Dashboard Views uses a config.js file for installation and configuration. This file controls the global behavior across your entire Sisense instance.

To locate this file:

You can edit the file's code directly in the user interface.

An array that determines if the Dashboard Views icon is displayed in the dashboard header, in the filter panel, or both. Dashboard Views options will also appear in the three-dot menu. The values in the array are not required to be in a particular order.

The default icon can be changed by uploading an SVG file, named bookmark_icon.svg to the QBeeQViews folder. You will be prompted to replace the existing file. The new icon image will be applied when the plugin is rebuilt, which should be done automatically.

The options included in the array allow Views to be shared with specific user groups.

When included in the array, the options are visible in the UI, but the list of eligible user groups is not displayed to users. The values in the array are not required to be in a particular order.

Defines an array of Sisense user groups that can create public Views for all users. Any users who are not included in the defined user groups will be able to see and use public Views, but will not have the option to create them.

An array that specifies user groups to include access to shared Views, allowing the use of wildcards. See Shared Views for more information about using this configuration, behavior, and use cases.

An array that specifies groups to exclude from accessing shared Views, allowing the use of wildcards. See Shared Views for more information about using this configuration, behavior and use cases.

Dashboard Views can be enabled or disabled globally for all dashboards using this configuration. Dashboard Views can be enabled or disabled for specific dashboards.

Dashboard groups allow a Designer to manually create a group and apply the same view across multiple dashboards.

As new dashboards are created using the same data model, Views will automatically be applied. Views can be disabled for specific dashboards if not needed.

Specifies the location of the Views icon in the filter panel.

Allows users to create Views either at the root model or using a specific perspective.

Related to importing Views and groups.

Sets the default value for the Server URL input field in the import popup. This should point to the environment from which Views or groups will be fetched (e.g., a development or staging server).

Related to importing Views and groups.

Controls the access and visibility of the Import Views and Import Groups in the dashboard menu

The encryption setting for data stored in the view collections. The default value is set to `false` to ensure compatibility with legacy collections created prior to this feature. Encryption only needs to be configured once, which will encrypt existing Views, and all new Views.

The system uses a variable called selectedNamingConvention to determine which naming convention to apply for text and language displayed in the plugin.

To locate this file:

Examples of old and new naming conventions

The passPhrase is a string value used to encrypt or decrypt view collections when useEncrypted is set to true.

Changes to the dashboard’s data model may remove columns, and thus filters that have been included in Dashboard Views.

Used to change the font-family for the Views plugin1wqq.

A setting to include or exclude primary filters as part of the view.

Determines whether users can choose to save their Widget Controller selections (e.g., dimensions, measures, break-bys) along with filters when creating a view.

Defines the default selection state of the “Include Widget Controller selections” option.

Customizes the label text that appears next to the “Include Widget Controller selections” checkbox in the view creation dialog.

Enables or disables a data validation check before applying a saved view. When active, this ensures that widgets referenced by the Widget Controller still contain valid data, helping prevent user errors caused by schema or data model changes.

Shared Views allow you to control view sharing by leveraging native Sisense user groups. It ensures Views are shared only with designated groups. This is particularly useful for OEMs serving multiple customers with diverse data access needs by creating Views that are shared only with designated user groups.

sharedViewsUserGroupsFilter and sharedViewsUserGroupsExcluded can be combined to target specific groups while excluding others.

sharedViewsUserGroupsFilter

Specifies user groups to include access to shared Views, allowing the use of wildcards. This is suggested when group naming conventions are consistent.

sharedViewsUserGroupsExcluded

Specifies user groups to exclude and prevent sharing Views with irrelevant groups, allowing the use of wildcards. This is suggested when naming conventions are inconsistent or non-existent

Users can import Views and view groups from a separate Sisense environment—such as development, staging, or production—directly through the dashboard. This simplifies dashboard promotion workflows by eliminating the need for manual scripts or post-import updates.

After providing valid credentials and clicking Submit, the application:

Create a dashboard group

To create a dashboard group:

Add a dashboard to a group

To add a specific dashboard to an existing group:

Remove a dashboard from a group

Delete a dashboard group

When Autogrouping is enabled in the configuration file, it automatically applies Views across all dashboards using the same data model.

If you manage multiple dashboards with the same data model, Autogrouping removes the manual effort of creating distinct dashboard groups, ensuring a seamless and efficient workflow.

Autogrouping and Filter Behavior Across Dashboards

If you have multiple dashboards using the same data model, Autogrouping helps by automatically organizing them—eliminating the need to manually create separate dashboard groups.

Controlling Filter Behavior

To limit filters to only those that match the existing data sources on each dashboard, use the OnlyUseExistingFilters option. This ensures that dashboards apply only relevant filters and avoid unwanted data inclusion.

To encrypt view collections:

When saved, this code will update the view collections from all dashboards.

To decrypt view collections:

When saved, this code will update the view collections from all dashboards.

If you are embedding your dashboards and hiding the header and/or the filter panel, you can still provide the Dashboard Views feature by adding a QBeeQ Views widget to your dashboard.

By default, both the Views and Create View buttons will display. In the designer panel, you can control the display label for each button.

Depending on the configuration, accessing Dashboard Views can be accessed from the dashboard header, filter panel or their respective three-dot menus.

To view the list of Views available to you, click the icon. Toggle between My Views and Other Views to see all Views available to you.

Before creating a new view, select and apply any filters to the dashboard that should be included as part of the view.

To create a new view:

Filters can then be removed and/or changed to create additional Views.

Users can set a view as the default view for a dashboard When the dashboard loads, the system checks whether a default view has been selected.

To delete a view:

When a view is deleted, it will be immediately removed from the Other Views list for all users.

Usage Analytics is available as a CSV download for Designers or Admins. The CSV contains information about all Dashboard Views that have been created and stored on the server. This file includes metadata about individual view filters (id, type, dashboardId, createdBy, etc.), user groups, and shared user groups.

To generate a usage analytics CSV:

When clicked, the file will automatically download.