Appearance
Model Diagnostics
Model diagnostics identify structural, reference, semantic, and metric-governance problems before a model is used in reports or AI-assisted analysis.
Open Diagnostics
A bar at the bottom of the canvas has two tabs, Model diagnostics and Metric bindings. It appears when the model has diagnostics, bound measures, or visible measures that are not bound to a metric, and it starts collapsed. Click Model diagnostics to expand it; the tab badges show the number of errors and warnings.
Use the severity controls and All categories filter to narrow the list. Select an issue to focus the modeler on the related table, relationship, field, Dimension, or Measure.
Severity levels
| Severity | Meaning | Recommended action |
|---|---|---|
| Error | A structural, reference, or governance problem that can make the model inconsistent. | Resolve it before use whenever possible. Saving requires an explicit override. |
| Warning | A likely modeling or compatibility problem that needs review. | Confirm the design and expected query result. |
| Hint | Missing semantic metadata or another recommended improvement. | Complete it for user-facing and AI-enabled models. |
What is checked
Diagnostics can report:
- Duplicate table aliases.
- Missing table or field metadata.
- Relationships that reference missing tables or fields.
- Empty calculated-column or calculated-measure expressions.
- Missing or invalid Measure aggregations.
- Unknown Measure references in calculated formulas.
- Isolated tables or disconnected Dimensions and Measure Groups.
- Relationship cycles in single-fact components. Components with multiple Measure Group tables are exempt from this cycle warning, so inspect each fact-to-Dimension route manually.
- Missing business descriptions or incomplete time settings.
- Missing, stale, drifting, or duplicate enterprise metric bindings.
Unused fields
For administrators, diagnostics also reports, at Info level, measures and attributes that no report uses: "Store Manager" is not used by any report. The rule reads the lineage usage records and runs only when all reports on the server are visible to you, so that a field used in another user's personal folder is never reported as unused. See Usage and Impact Analysis.
Diagnostics during Save
When you save a model:
- Warnings and hints do not block the save operation.
- Errors open a detailed review dialog.
- You can return to the modeler or explicitly choose to continue saving.
- Server-side verification runs after the client diagnostics.
An Error requires an explicit override; it is not an absolute save block. Use Continue to save only when you understand the impact. A model with no tables cannot be saved.
Review metric bindings
The Metric bindings tab summarizes model Measures and calculated measures linked to Metrics Library. Compare definition asks the configured AI service to compare an implementation with the enterprise metric's business definition. Use Compare all to run the comparison for all eligible bindings. If a row shows Not registered, save the model before retrying.
A successful Compare definition or Compare all also moves the binding to the metric's current version and updates the measure's version reference, so a row no longer shows an older bound version after the comparison. The comparison does not change the measure's formula or aggregation. It can fail when the AI service is unavailable, misconfigured, unauthorized, or times out.
While the model has visible measures that are not bound to a metric, the tab also shows Generate metrics from this model to users with administrator or metric-creation permission. It registers the selected measures as draft metrics and binds them; see Metrics Library.
Before using the model
- Resolve all Errors, including structural, reference, and metric-governance errors.
- Verify every relationship's keys, join type, and cardinality.
- Review disconnected Dimensions and Measure Groups.
- Check calculated-measure references and formats.
- Add descriptions to user-visible Dimensions and Measures.
- Review enterprise metric bindings and definition consistency.
- Save, then validate representative totals and drill paths in a report.