If you’re seeing this error when viewing a chart on a dashboard, a few things are likely happening:
- You have Viewer permissions in Omni (permissions docs).
- The queries on that dashboard are not built off a “predefined Topic” in the shared model. This includes:
- SQL queries (docs)
- Queries built off All Views & Fields (not built off a Topic)
- Queries in workbooks that have altered Topics or Relationships
In other words, this happens when a Querier or Connection Admin has made changes in the workbook that considerably alter the shared model. To ensure no sensitive information is inadvertently shared, Omni restricts Viewers from seeing the charts in that workbook. For more on Permissions, check out our docs here.
How to fix the warning message
The resolution here is usually simple! There are a few options:
- Keep the charts restricted
The Querier / Admin that made these Workbook changes might not be aware that you had Viewing access to the dashboard and may actually want to restrict these charts from you. It’s best to check with them to make sure they were indeed expecting you to have view access.
- Promote these changes to the Shared model
If the Querier / Admin does want you to be able to view this dashboard, one way to resolve the warning is for them to promote these changes to the Shared model. They can do so by opening the Workbook Model Changes section while editing a workbook and either (1) Promote all changes to shared, or (2) Promote individual changes and delete other changes.
Note: Fields based purely on other modeled fields (i.e. measures created from the quick aggregation menu, or a field defined as ${field_a} + ${field_b}) will not lead to restriction. These fields do not need to be promoted.
- Enable AccessBoost
If you just want to be able to view this dashboard in particular, your Admin can enable AccessBoost on that dashboard. This means that the dashboard will ignore users’ database connection roles, in effect overriding their usual Permission level to enable access to a specific dashboard. You can read more about how to enable AccessBoost in our docs here.