Video | Tableau | Data visualisation | Data prep

Understanding the grain of your data in Tableau

Understanding what your data is about is critical to make sure you calculate the right aggregate values.

Part of Tableau Key ConceptsTableau Level of detail functions
Watch on YouTube
  • The Orders count field actually counts rows in the Orders table, not distinct orders, so a single order can span multiple product rows
  • Superstore operates at the product level of detail, meaning each row is a product within an order rather than the order itself
  • Average sales in Tableau is really the average product value, calculated as total sales divided by the number of rows in the dataset
  • To get the true average order value you divide total sales by the distinct count of orders, which differs from the default average
  • Each logical table in the data model can have its own grain (Orders at product level, Returns at order level, People at regional level), and Tableau handles the aggregation across relationships

Understanding the grain (the level of detail) of your data tells you what each row actually represents, which determines what Tableau's aggregations, like averages, really mean. Get this wrong and you'll misread figures like 'average sales' as something they're not.

Tim uses the Sample Superstore dataset, dragging Order ID and Sales into a table to investigate what each row represents before he covers order of operations and LOD calculations in upcoming videos.

The Breakdown
  1. Why grain matters before LODs 0:00

    Before tackling order of operations and LOD calculations, you need to understand granularity: the level of detail each row in your data represents. This decides how Tableau aggregates everything, so it's worth investigating for any dataset you work with.

  2. A field name can mislead you 1:41

    A count field named after a table (like an 'Orders' count) doesn't necessarily count what you think — it counts rows in that table. Always check what a row actually represents rather than trusting the field's label.

  3. Use the summary window as a live calculator 2:56

    You can enable the summary window from the Worksheet menu and drag it to a convenient spot, such as above the filters shelf. Select cells in your view and it shows sum, average, min, max and median instantly, working off what's displayed rather than the underlying data.

  4. Drill into the detail to find the true grain 4:03

    Click into the summary/detail view of a data point to see the individual rows behind it. This is how you confirm what each row represents — in Superstore's case, each row is a product within an order, not the order itself, even though the table is called 'Orders'.

  5. Average sales is really average row value 5:48

    Because Tableau always aggregates at the grain you're working at, 'average sales' is calculated as total sales divided by the number of rows — the product level here — not divided by the number of distinct orders. Don't assume an average means what its label suggests without checking the underlying grain.

  6. Calculate a true average order value 8:45

    To get the average value per order rather than per product row, divide total sales by a distinct count of orders instead of relying on the default average. This is the kind of manipulation LOD calculations exist to handle, since Tableau won't do it for you automatically.

  7. Each table in your data model can have its own grain 9:53

    When using relationships in the data model, different logical tables can sit at different levels of detail — one table at product level, another at order level, another at regional level. Check for hidden fields (via 'show hidden fields') to see what a relationship is actually built on, since Tableau may rename or hide the joining column.

Worth Knowing
  • A field can be named after its source table rather than what it counts, so a count labelled 'Orders' may just be counting rows, not distinct orders.
  • Averaging cells that are themselves averages gives a misleading result — the summary window operates on displayed values, not raw data.
  • Hidden fields in the data model (visible only once you tick 'show hidden fields') often reveal the real basis of a relationship between tables at different grains.
Use It When

Reach for this whenever a number in your view looks off or you're about to build an LOD calculation — check what a single row in your data actually represents before trusting any default aggregate.

How this Rollup was made provenance & method

A Rollup is drafted by AI from the video's transcript, then reviewed and edited by Tim. Everything used to produce this one is listed below — the model, the exact prompt, and the source video — so the process is transparent and reproducible.

Transcription
On-device — NVIDIA Parakeet v3 for recent videos, OpenAI Whisper large-v3 for earlier ones. The transcript never leaves the machine or gets published.
Drafting
Claude Sonnet 5 in the cloud, from that transcript.
Prompt
The exact Rollup prompt (v2) — the full system prompt, unedited.
Source video
Watch on YouTube
Drafted
5 July 2026 at 09:38
Reviewed & edited
5 July 2026 at 09:41 · by Tim Ngwena

Model + prompt + video is everything you'd need to recreate a Rollup like this yourself. The one thing we don't share is the transcript.

Rights. The video and its transcript are the property of TN Media Ltd. Unauthorised use or download is prohibited. © TN Media Ltd.