The Data Pane & The Format Pane
The Data pane is your model's public interface — what report authors see and can use. The Format pane is where a visual stops looking like a default and starts looking deliberate. This lesson covers what the field icons mean, how to organise the pane, and how Format is actually structured so you stop hunting through it.
Learning Objective
These two panes are used constantly and understood shallowly. Knowing the field icons prevents a class of errors; knowing Format's structure saves you real time on every report you ever build.
- Identify every field icon in the Data pane and what it implies
- Organise a model with display folders, hierarchies and hidden fields
- Navigate the Format pane's two-tab structure without hunting
- Apply formatting consistently using themes and copy-paste rather than by hand
- Explain why model-level formatting beats visual-level formatting
Why This Matters
Two costs of not knowing this.
The icon cost. A field with a Σ beside it will be summed when you drag it in. If you cannot read that at a glance, you will sum things that should not be summed, and the result will look fine. The icons are a warning system and most people never learn to read them.
The formatting cost. Formatting a visual by hand takes a few minutes. Twelve visuals takes an hour, and they still end up subtly inconsistent — three different title sizes, two different fonts. Themes and copy-paste reduce that hour to about five minutes and make consistency automatic.
Concept
Reading the Data pane
Every field carries an icon that tells you what it is. Learning these six takes two minutes and pays back permanently.
| Icon | Means | Implication |
|---|---|---|
| Σ (sigma) | Numeric column with a default aggregation | Dragging it in will sum it. Check whether that is what you want |
| Calculator | A DAX measure | Calculated at query time in filter context. This is what you want for ratios |
| Calendar | A date or date/time column | May have a hierarchy beneath it if Auto date/time is on |
| Globe | A column with a geographic data category | Map visuals will use it for geocoding |
| Italic text | A calculated column or calculated table | Added with DAX rather than loaded. Materialised per row, so it costs memory |
| Two-arrow / hierarchy icon | A hierarchy | Drag it in and the visual supports drill-down through its levels |
Year, score columns, ID numbers and rates. Seeing it should prompt the question should this be summed? If the answer is no, fix it at model level with Summarization › Don't summarize, so it can never happen again.Organising the Data pane
A model with sixty fields in a flat list is unpleasant to use. Four tools fix that:
| Tool | How | Effect |
|---|---|---|
| Hide in report view | Right-click a field | Removes it from the pane for report authors. Still works in DAX and relationships |
| Display folders | Properties panel → Display folder | Groups fields into collapsible folders. Use Parent\Child for nesting |
| Hierarchies | Right-click a field → Create hierarchy, then drag others in | Bundles related levels — Category › Subcategory › Product — for drill-down |
| Descriptions | Properties panel → Description | Appears as a hover tooltip in the pane. The only documentation people actually see |
A measures table
A common professional pattern: create an empty table (Home › Enter data, one blank column, name it something like _Measures), then set every measure's Home table to it and hide its dummy column. All your measures then live in one place at the top of the Data pane rather than scattered across fact tables.
The Format pane's structure
The Format pane is not a flat list. It has two tabs, and knowing which one owns what removes most of the hunting.
| Tab | Controls | Examples |
|---|---|---|
| Visual | Things specific to this visual type | X axis, Y axis, legend, data labels, columns/bars, markers, gridlines, slicer settings, matrix row headers |
| General | Things every visual has | Title, subtitle, background, border, shadow, header icons, alt text, and Properties (exact size and position) |
Properties — exact size and position
Under General › Properties you can type exact X, Y, width and height values. For precise layouts this beats dragging entirely: set one visual's position, then type matching values into the others. Module 8 uses this for grid layouts.
The search box
The Format pane has a search box at the top. Typing "label", "border" or "tooltip" filters to matching settings. On visuals with dozens of settings this is much faster than scrolling.
Formatting at the right level
| Level | Set it with | Applies to | Use for |
|---|---|---|---|
| 1. Theme | View › Themes (or a custom JSON theme) | Every visual in the report | Colour palette, default fonts and sizes, background |
| 2. Model | Column tools / Measure tools › Format | Every visual using that field | Currency, decimal places, percentage, date format |
| 3. Copied visual | Format one visual, then Ctrl+C / Ctrl+V | The new visual | Everything else — titles, labels, borders |
| 4. Individual visual | The Format pane | That visual only | Genuine one-offs, and only after the three above |
There is also the format painter on the Home ribbon: select a formatted visual, click the painter, click the target. It copies formatting without copying fields, which is useful when the target already has the right data.
Visual Explanation
The same card visual at four formatting levels, showing what each one contributes.
| Level applied | What the card shows | Effort |
|---|---|---|
| Nothing — default | 6311491.41, default grey title "NetSales" | None |
| + Theme | Same number, but brand font and colour | Once per report |
| + Model format string | $6,311,491.41 — currency, two decimals | Once per field |
| + Visual formatting | $6.31M, title "Total Revenue", subtle border | Once, then copy |
Display folders in practice
| Flat list (before) | Organised (after) |
|---|---|
| Total Revenue, Total Profit, Profit Margin %, Total Orders, AOV, Revenue YoY %, Revenue YTD, Active Customers, Discount Rate, NetSales, COGS, Profit, Quantity, UnitPrice, Discount, OrderID, CustomerKey, ProductKey, StoreKey… | 📁 Core — Total Revenue, Total Profit, Total Orders, Active Customers 📁 Ratios — Profit Margin %, AOV, Discount Rate 📁 Time — Revenue YoY %, Revenue YTD raw columns and keys: hidden |
Power BI Demonstration
NetSales → Column tools › Format › Currency, 2 decimals. Check a visual using it — the formatting is inherited._Measures, Load. Then select each measure and set Measure tools › Home table to it. Hide the dummy column.Core. Repeat for several. They group in the pane.Category → Create hierarchy. Then right-click Subcategory → Add to hierarchy → the one you made. Drag the hierarchy into a chart and use the drill buttons.Example Dataset
This lesson is conceptual and needs no download — it uses the sample data shown inline above. The next lesson that requires a file will link it here.
You can still browse every dataset in the course from the dataset library.
Step-by-Step Exercise
Turn a messy model into an organised one. Use the five-table model from Lesson 3.
NetSales, COGS, Profit, UnitPrice, UnitCost. Percentage on Discount._Measures with Enter data. Write three measures — Total Revenue, Total Profit, Total Orders — and set their home table to it.Core display folder.Expected Result
A Data pane that a stranger could use correctly without asking you anything.
✓ Currency and percentage formats set once, at model level
✓ Measures grouped in folders, in a
_Measures table✓ A working Category › Subcategory › Product hierarchy
✓ No keys or raw fact columns visible
✓ Four consistently formatted cards built from one, not four
If you drag any visible field into a visual now, you should get something sensible by default. That is the test of a well-organised model: the obvious action is the correct action.
Common Mistakes
Fix: Theme → model format strings → format one visual → copy it. Reach for the per-visual Format pane only for genuine one-offs.
Fix: Remember the split: Visual = specific to this chart type. General = every visual has it. Or just use the search box.
Fix: Treat the Σ as a prompt. Fix genuinely non-summable columns at model level so the question never arises again.
Fix: Hidden fields work perfectly in DAX and relationships. Hiding only affects the Data pane. Hide freely.
Fix: A hierarchy needs a genuine parent-child relationship at every level: Category contains Subcategory contains Product. Year contains Quarter contains Month. If a child can belong to two parents, it is not a hierarchy.
Professional Tip
Spend thirty minutes on this once and every future report starts consistent and on-brand with zero per-visual work. It is the single highest-leverage formatting investment available, and almost nobody does it because the payoff is on the second report rather than the first.
Two smaller habits:
- Set alt text on every non-decorative visual. General › Alt text. It is what a screen reader announces, and it takes fifteen seconds. Module 7 Lesson 6 covers accessibility properly.
- Use Properties for exact positioning rather than dragging, once a layout is settled. Typed coordinates are reproducible; dragged ones are not.
Knowledge Check
Knowledge Check
5 questions. Answer each one to see why the right answer is right.
Where is a visual's Title setting?
A field in the Data pane shows a Σ icon. What does that tell you?
You hide a key column from report view. What happens to the relationship that uses it?
What is the most efficient order for applying formatting to a report?
Which of these is a valid hierarchy?
Practical Challenge
Design a Data pane a stranger could use correctly
Take the five-table model and organise it so that a report author who has never seen it could build a correct visual on their first attempt, without asking you a single question. Then write a short note justifying each decision.
- Every field that remains visible should be safe to drag in — the obvious action produces the correct result
- Measures organised into at least three display folders with meaningful names
- At least two hierarchies that genuinely nest
- Descriptions on every measure
- A written note explaining why each hidden field is hidden
- A written note on one naming change you made and why
The test to apply to each visible field: if someone drags this into a visual without thinking, do they get something correct?
- A key column → they get a meaningless count. Hide it.
- A raw
NetSalescolumn with a measure already defined → they get an implicit sum that bypasses your definition. Hide it. Discountas a rate → they get a summed rate. Either hide it or band it in Power Query.Regionwhen it exists in two tables → they get an ambiguous answer. Rename both.
Solution
Try the challenge properly before opening this. Reading a solution you have not attempted feels like learning, but it is not.
A model answer
Display folders
| Folder | Measures | Rationale |
|---|---|---|
| Core | Total Revenue, Total Profit, Total Orders, Active Customers | The base additive measures everything else builds on. First folder alphabetically and conceptually |
| Ratios | Profit Margin %, Average Order Value, Discount Rate | Non-additive measures grouped together, which also serves as a quiet reminder that they behave differently |
| Time | Revenue YoY %, Revenue YTD, Revenue Prior Year | Time-intelligence measures, all of which depend on the date table |
| _Internal | Any helper measures not meant for direct use | The underscore sorts it last. Better still, hide these entirely |
Hierarchies
- Product: Category › Subcategory › ProductName. Each level genuinely contains the next, so drill-down answers "which subcategory within Electronics, and which product within that".
- Date: Year › Quarter › MonthShort. Same property. Note this requires MonthShort to have its sort-by column set, or drilling produces alphabetical months.
Hidden fields and why
| Hidden | Reason |
|---|---|
All *Key columns in both fact and dimensions | Dragging a key into a visual produces a meaningless count of internal identifiers. They exist for relationships, not for reporting |
Sales[NetSales], [COGS], [Profit], [Quantity] | Measures now define these. Leaving the raw columns visible means two routes to the same number, one of which bypasses the agreed definition — the fastest way to get two people reporting different revenue |
Sales[UnitPrice] | Duplicated from the product dimension at transaction time. Anyone averaging it gets an unweighted average, which is wrong. If price analysis is needed, it should be a properly weighted measure |
Sales[Discount] | A rate. Summed it is meaningless; averaged it is unweighted. Replaced with a banded Discount Band column built in Power Query, plus a weighted Discount Rate measure |
Date[MonthNumber], [DayOfWeek], [QuarterNumber] | Sort-by helper columns. They must exist for ordering to work, but nobody should ever put them on a chart |
The naming change
Region existed in both the Customer and Store tables. Left alone, two visuals labelled "Revenue by Region" would show different numbers and neither would be wrong — one slices by where the customer lives, the other by where the store is.This produces no error, no warning and no visible breakage. It produces a stakeholder who notices two charts disagreeing and concludes the report cannot be trusted. Renaming both costs thirty seconds and removes the ambiguity permanently.
This is genuinely what separates a model built by someone experienced from one built by someone competent. The competent model works if you use it correctly. The experienced model is hard to use incorrectly.
Lesson Summary
- The Data pane's icons tell you what a field is. The Σ means it will be summed — treat it as a prompt to check.
- Organise with hidden fields, display folders, hierarchies and descriptions. A
_Measurestable keeps measures in one place. - The Format pane has two tabs: Visual for chart-type-specific settings, General for things every visual has — including Title.
- Format at the highest level that works: theme → model format strings → copy a formatted visual → per-visual last.
- Hidden fields still work in DAX and relationships. Hide keys and raw fact columns freely.
- A hierarchy needs genuine nesting at every level. Category › Subcategory › Product works; Category › Region does not.
- A well-built model makes the obvious action the correct action.
Syllabus topics delivered
Progress
Marking a lesson complete stores your progress in this browser and updates your BitWithBite learner dashboard. Nothing is uploaded anywhere.