Aglet

Triage Incorrect Units and Labels in Reports

A correct number can become misleading when its label implies another unit. Begin with the measure definition and a known example, then compare data transformation and presentation separately. Seconds displayed as milliseconds and a percentage displayed as a raw ratio are different boundary problems even when both look like a simple labeling issue.

Establish what is happening

  1. Identify the measure’s actual unit

    Choose a controlled value whose meaning and magnitude are independently known. Record the source unit, aggregation, and expected displayed unit. Compare the underlying result with its axis, tooltip, and table label, keeping a scaled display separate from a change to the number returned by the query.

  2. Trace scaling and formatting

    Follow any conversion, normalization, or display multiplier between the source and the report. Record where the unit changes and whether the accompanying label changes with it. A familiar abbreviation does not prove every series uses the same unit, especially when values come from differently defined measures.

  3. Compare another report surface

    Inspect the same measure in a table, drilldown, or supported export. Check whether its unit remains explicit and consistent. If only one chart differs, narrow the next investigation to that presentation path; if several surfaces share the mismatch, retain the measure definition or transformation as a candidate boundary.

What to carry forward

End with the source unit, intended display unit, exact transformation, and first inconsistent label or value. State any ambiguous measure definition. The next owner should know whether to inspect calculation, scaling, or presentation rather than changing a suffix until one example looks familiar.

Technical background: Metabase documentation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow