Opening the Content Validator
In Cube Cloud, navigate to the Data model module and select the Content Validator tab.How validation works
The Content Validator checks every workbook in the deployment. For each workbook, it validates the workbook’s draft reports as well as the report snapshots of its published dashboard. Each report’s query is checked with the same query parser the report editor uses, so a reference flagged here is exactly the broken reference a viewer would hit when opening that report. The Content Validator also checks the conditions of scheduled tasks. A task is flagged when its condition’s Measure or Time dimension is no longer a measure or a dimension of its view in the data model. Scheduled tasks are checked only when AI is available in your session, and only the tasks you can see (see Managing tasks). If the tasks can’t be loaded, the page says so, and the tasks aren’t checked. Validation is branch-aware: reports and scheduled tasks are checked against the data model of whatever context you are currently in — your development mode, a shared branch, or production. The page header names the context you are validating against, so you always know which version of the model the findings apply to.The Content Validator uses the full data model, ignoring visibility settings
and access policies. A report referencing a member that is hidden with
public: false or restricted by an
access policy is not flagged — the member still
exists in the model. Only references to members that are truly gone are
reported.Reviewing findings
Each finding is one row in the findings table:
There are three kinds of broken references:
- Missing field — the report references a member (a measure or a dimension) that no longer exists in an otherwise valid view.
- Missing view — the report queries a view that no longer exists in the data model.
- Missing field in a scheduled task — the condition of a scheduled task references a measure or a time dimension that no longer exists. These rows show a calendar icon and a Scheduled task badge.
Comparing with production in Dev Mode
In development mode, findings are compared with the production data model:- Findings that are broken on your branch but not in production show a New badge, and the summary says how many were introduced on this branch. Use the All / Introduced here / Pre-existing filter to focus on either.
- A scheduled task whose instructions mention, by name or title, a member that your branch removed is listed as May be affected, with the error Instructions mention ”…”, removed on this branch. Instructions are free text, so this is a hint, not a proof: these rows aren’t counted as broken references, and the summary counts them separately.
Fixing broken references
How you fix a finding depends on whether it is in a draft report, a published dashboard snapshot, or a scheduled task:- Draft reports are editable in place. Each draft finding offers Open, Replace, and Delete actions.
- Published dashboards are immutable snapshots — they only change when their dashboard is republished. Published findings offer only an Open action; to fix one, update the draft report in its workbook and republish the dashboard.
- Scheduled tasks offer only an Open action. To fix one, open the task and pick an existing measure or time dimension in its condition, or, for a May be affected row, update its instructions. Only the task’s creator, an admin, or a role granting Manage all scheduled tasks can edit it.
Open
Open navigates to the content itself: the report in its workbook for a draft finding, the live published dashboard for a published finding, or the task’s detail page for a scheduled task finding.Replace
Replace swaps the broken reference for an existing one across the report’s saved query. Clicking it opens a dialog with a searchable picker of valid replacements — members of the same view for a missing field, or other views for a missing view.- If several draft reports share the same broken reference, the dialog offers a Replace in all affected reports checkbox (enabled by default) so you can fix them all in one action.
- If a published dashboard references the same member, the dialog notes that it will keep its current snapshot until the dashboard is republished.
Delete
Delete permanently removes the report from its workbook — use it for reports that are no longer worth fixing. A confirmation dialog is shown before anything is deleted, and validation re-runs afterwards.Scope and limitations
- The Content Validator validates reports whose queries are stored as
semantic SQL. Some reports use advanced semantic queries
that the parser cannot fully read, e.g., a
WITHclause, a join, or a subquery. For such a report, the Content Validator still checks the views it reads from: everyFROMandJOINtarget that is neither a view nor a CTE of the query is flagged as a missing view. Field-level checks do not run for these reports. - A report is counted as not checked when the parser cannot fully read its query and no missing view is found in it — it is neither flagged as broken nor asserted to be clean. When this happens, the summary shows a N reports could not be checked note.
- Validation covers each workbook’s draft reports and its published dashboard snapshots.
- Replace and Delete act on draft reports only. Fixing published content is a two-step process: fix the draft, then republish the dashboard.
- For scheduled tasks, only conditions are checked against the data model. Instructions are free text and are checked only in Dev Mode, and only for members removed on the branch.