Insights Dashboards Best Practices

The following practices are recommended when configuring Insights Dashboards. For more information on configuring Insights Dashboards, see Building and Editing Insights Dashboards.

GUID vs ID

In Graph visuals, pull in GUID from the data table instead of ID. However when creating Count Card visuals, if you are using the GUID for the primary object of the table, apply the Count function instead of the Count (Distinct) function to that GUID.

Spelling and Capitalization

Insights Dashboard values are case sensitive. Ensure that you are using the correct spelling and capitalization when searching for attribute values on the Filters pane.

Attribute Value Filtering

Apply the following practices for attribute value filtering for graphics and slicers:

  • Fields from the Attributes Configuration data table should be added to the Filters on this page section of the Filters pane.

  • Attribute Names from the Attributes for Graphics & Slicers data table to the Filters on this visual section of the Filters pane.

    Note:

    Ensure that you select the attribute that you want to filter on. Do not select Blank.

Apply the following practices for attribute value filtering for tables:

  • Attribute Names from the Attribute Value Tabular data table should be added to the Filters on this visual section of the Filters pane.

Insights Default Experience

Set Insights Dashboards as the default experience for all users who have permissions to view dashboards. Insights Dashboards can be enabled by default through Global Settings. For more information, see Insights Settings.

Related Assessments or Inventory Names for Risks

Use fields within the Risk Related Objects data table for use cases where you want to include related assessments or inventory names for risks.

Data Table Relationships

To understand the relationships between data tables, see Insights Data Models, Scopes, and Permissions.

Table Visuals

When adding columns based on different objects in a single Table visual, use columns from the same data tables, if possible. This improves performance and provides faster loading times. If two different data tables are used, it will only bring in values that are present in both data tables.