Site Validation Guide

The One Model Site Validation tool provides Admin users a way to review the configuration of your company’s One Model instance. Admins, Data Engineers, and One Model teams use the Site Validation page to view the list of errors and warnings in the different components of your site, and find possible solutions to address those warnings and resolve errors. This is an especially useful page to review after making changes to your One Model instance. 

Admins with the permission CanViewSiteValidation will find the Site Validation page under the Admin tab of the main navigation bar. 

Site Validation page

Admins can drill into the Validations for each component, review the messages then click on the Action icon to review next steps. The following table lists all of the components available in Site Validation and the primary manager of that component, whether One Model or your company Admin. 

Component Primary Manager
  Data Engineer Admin 
Drill Through Columns  
Security Rules  
Time Dimensions  
Data Warehouse Relationships  
Slowly Changing Dimensions  
Data Sources  
Data Warehouse Tables  
Geospatial Dimensions  
Data Destinations  
Insight Library  

** Note** if Admins (or one their team members e.g. data analyst) work in their own processing script, the responsibility for these features would be shared between them and their data engineer.

Using Site Validation

To access Site Validation: 

  1. Ensure you have the permission  CanViewSiteValidation enabled
  2. Click the Admin tab in the top navigation bar to open the dropdown menu, 
  3. Scroll down the menu then click on Site Validation to open the Site Validation page. 

Once in the Site Validation page, scroll down to view the list then click on the Validation tab for more information.  A message box will appear with details about any errors or warnings along with options to fix or resolve. 

Clicking this button displays a detailed list of all errors or warnings associated with that feature.


Errors mean there is an issue that could break functionality, or would likely cause unexpected/wrong results.

Warnings mean there could be an issue that shouldn’t break functionality, but might cause performance problems or similar.


Messages describe what exactly is causing the error or warning. 


Takes you to the specific page where you can make the modification to correct the error or warning.

Takes you to the storyboard where the query needing modification is located.

Provides you with a list of the invalid nodes(s).

If your site is not set up to automatically cache site validation results (confirm this on the Admin > Company page), clicking the refresh button will update the Site Validation page so it shows the most up to date errors and messages. This button should also be clicked after making changes to confirm if the change you made fixed the error or warning. 

Process using a Metrics example

If we look at Metrics, we can see that there are 9 errors and 0 warnings. 

If we click Validations, this opens the messages box.

Next, if we select the following message,

And then click on the icon in the Actions column, it will bring us to the Build/Edit Metric page.

From here, we can review the error and take steps to rectify and resolve. In this case, the suggested action is to save the metric. But, before we do, we should check for invalid filters and review the filters in case something has changed in the underlying dimension. 

Click the save icon in the left hand menu. 

Go back to the Site Validation page. Refresh the Site Validation page by clicking the Refresh icon at the top right of the page. Your resolved error should not be listed.

** Tip ** Ensure the Cache Site Validation Results checkbox is enabled so that the Company cache will automatically refresh in the background to keep your instance up to date with the most recent data. 

Common Messages - for Admins




The <metric name> metric references a node from the <dimension name> dimension that does not exist: <node ID> The metric listed in the error message is set up to include a filter from a dimension. The dimension node used in at least one filter no longer exists in that dimension.Remove the invalid node from the metric’s Dimension Filter section of Build/Edit Metric.*
The <metric name> metric references a column that does not exist: <column name> The metric listed in the error message is set up to include a Metric Definition that no longer exists. Remove the invalid field from the Metric Definition section of Build/Edit Metric. 


* When editing a metric in Explore, there may be a message stating ‘Invalid filters were found, and were not included in this Metric. Saving will remove the invalid filters and prevent this message from appearing.’

 Before you hit the save button, we recommend that you review your filters.




The '<tile name>' Tile on the ‘<storyboard>' Storyboard is invalid: refers node(s) from dimension '<dimension name>' that do not exist In the Explore query, identify the node in the dimension that is selected and no longer valid, and remove it from the selection.
The '<tile name>' Tile on the '<storyboard page name>' Page of the '<storyboard name>' Storyboard is invalid: table <table name> does not exist

In the Explore query, identify the additional column field that is from a table that no longer exists and remove it from the Additional Columns list.

Hint: Find the fields in the query that look like this:

Security Rules:



The '<role name>' role has a rule that references a node from the '<dimension name>' dimension that does not exist: <dimension node> On the Data Access Roles / Rules page, update the nodes in the Rules so the invalid ones are no longer selected.

Drill Through Columns: 



The '<group name>' group contains references to a column <column name> that does not exist On the DrillThrough Columns page, remove the column that no longer exists from the table that was using it. 

Please ignore any Site Validation messages related to any of the components managed by the One Model team. 




Was this article helpful?

0 out of 0 found this helpful



Please sign in to leave a comment.