Home Course home Curriculum Learner dashboard Skill tree Business projects Datasets Final project
🖥️ Module 1 · Power BI Desktop Beginner LESSON 09 / 72

The Data Pane & The Format Pane

26 min 5 quiz questions 1 practical challenge 4 syllabus topics

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.

Lesson 9 of 72 · Power BI Desktop 12%
01

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.

By the end of this lesson you will be able to
  • 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
02

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.

The professional pattern
Set formatting at the highest level that works: theme first, then model-level format strings, then a formatted visual you copy. Reach for the per-visual Format pane last, for the things that genuinely differ. Most beginners do this in exactly the reverse order.
03

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.

Field icons
IconMeansImplication
Σ (sigma)Numeric column with a default aggregationDragging it in will sum it. Check whether that is what you want
CalculatorA DAX measureCalculated at query time in filter context. This is what you want for ratios
CalendarA date or date/time columnMay have a hierarchy beneath it if Auto date/time is on
GlobeA column with a geographic data categoryMap visuals will use it for geocoding
Italic textA calculated column or calculated tableAdded with DAX rather than loaded. Materialised per row, so it costs memory
Two-arrow / hierarchy iconA hierarchyDrag it in and the visual supports drill-down through its levels
The Σ is the one that matters
It appears on any numeric column Power BI thinks is summable — including 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:

Organisation tools
ToolHowEffect
Hide in report viewRight-click a fieldRemoves it from the pane for report authors. Still works in DAX and relationships
Display foldersProperties panel → Display folderGroups fields into collapsible folders. Use Parent\Child for nesting
HierarchiesRight-click a field → Create hierarchy, then drag others inBundles related levels — Category › Subcategory › Product — for drill-down
DescriptionsProperties panel → DescriptionAppears 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.

This is a convention, not a requirement. Some teams prefer measures to sit on the fact table they relate to. Either is defensible; being consistent matters more than which you choose.

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.

The two Format tabs
TabControlsExamples
VisualThings specific to this visual typeX axis, Y axis, legend, data labels, columns/bars, markers, gridlines, slicer settings, matrix row headers
GeneralThings every visual hasTitle, subtitle, background, border, shadow, header icons, alt text, and Properties (exact size and position)
Title is under General, not Visual
This trips up nearly everyone. The title feels like it belongs to the visual, but because every visual has one it lives under General. Same for background, border and alt text.

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

Where to set formatting, in order of preference
LevelSet it withApplies toUse for
1. ThemeView › Themes (or a custom JSON theme)Every visual in the reportColour palette, default fonts and sizes, background
2. ModelColumn tools / Measure tools › FormatEvery visual using that fieldCurrency, decimal places, percentage, date format
3. Copied visualFormat one visual, then Ctrl+C / Ctrl+VThe new visualEverything else — titles, labels, borders
4. Individual visualThe Format paneThat visual onlyGenuine 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.

04

Visual Explanation

The same card visual at four formatting levels, showing what each one contributes.

Formatting layered up
Level appliedWhat the card showsEffort
Nothing — default6311491.41, default grey title "NetSales"None
+ ThemeSame number, but brand font and colourOnce per report
+ Model format string$6,311,491.41 — currency, two decimalsOnce per field
+ Visual formatting$6.31M, title "Total Revenue", subtle borderOnce, then copy
The point of the table
Only the last row needs per-visual work, and even that gets copied to the next eleven cards. If you find yourself formatting the twelfth visual by hand, something has gone wrong with your process.

Display folders in practice

Before and after organising a Data pane
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
05

Power BI Demonstration

Read the icons in your model
Open the Data pane and go through every field. Note which carry a Σ. For each, ask whether summing it means anything.
Fix the ones that should not sum
Table view → select the column → Column tools › Summarization › Don't summarize. The Σ disappears.
Set a model-level format string
Select NetSales → Column tools › Format › Currency, 2 decimals. Check a visual using it — the formatting is inherited.
Create a measures table
Home › Enter data. Leave one blank column, name the table _Measures, Load. Then select each measure and set Measure tools › Home table to it. Hide the dummy column.
Add display folders
Select a measure → Properties panel → Display folder → type Core. Repeat for several. They group in the pane.
Create a hierarchy
Right-click 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.
Apply a theme
View › Themes and pick one. Every visual updates. Note how much this does for free.
Explore Format's two tabs
Select a bar chart, open Format. Switch between Visual and General. Find the title under General, and the data labels under Visual.
Use the Format search box
Type "label" in the search box at the top of the Format pane. Only label-related settings remain.
Set exact position
General › Properties. Type X 40, Y 120, Width 400, Height 260. Repeat with matching values on another visual for a precise layout.
Copy formatting with the format painter
Format one visual well. Select it, click Home › Format painter, then click another visual. Formatting transfers without the fields.
Select visualFormat paneGeneralTitle
06

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.

07

Step-by-Step Exercise

Turn a messy model into an organised one. Use the five-table model from Lesson 3.

Audit the icons
List every field showing a Σ that should not be summed. Fix each with Don't summarize.
Set format strings at model level
Currency with 2 decimals on NetSales, COGS, Profit, UnitPrice, UnitCost. Percentage on Discount.
Build a measures table
Create _Measures with Enter data. Write three measures — Total Revenue, Total Profit, Total Orders — and set their home table to it.
Organise with folders
Put the three measures in a Core display folder.
Create the product hierarchy
Category › Subcategory › ProductName. Test drill-down in a bar chart.
Hide everything a report author does not need
All key columns, all raw fact columns now covered by measures, and the sort-by helper columns in the date table.
Apply a theme and format one card properly
Then copy that card three times and swap the measure in each.
08

Expected Result

A Data pane that a stranger could use correctly without asking you anything.

What 'done' looks like
✓ No Σ on any column that should not be summed
✓ 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.

09

Common Mistakes

Formatting each visual by hand
Twelve visuals, twelve rounds of setting fonts, colours and title sizes — and they still end up inconsistent.

Fix: Theme → model format strings → format one visual → copy it. Reach for the per-visual Format pane only for genuine one-offs.
Hunting for Title under the Visual tab
Title, subtitle, background, border and alt text are all under General, because every visual type has them.

Fix: Remember the split: Visual = specific to this chart type. General = every visual has it. Or just use the search box.
Ignoring the Σ icon
Dragging in a field with a Σ and accepting whatever number comes out, without asking whether summing it means anything.

Fix: Treat the Σ as a prompt. Fix genuinely non-summable columns at model level so the question never arises again.
Hiding fields you still need in DAX
Hesitating to hide key columns because a measure references them.

Fix: Hidden fields work perfectly in DAX and relationships. Hiding only affects the Data pane. Hide freely.
Creating hierarchies that do not nest
Bundling Category and Region into a hierarchy. They are independent dimensions, not levels of one thing, so drilling produces confusing results.

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.
10

Professional Tip

Build a custom theme JSON once, reuse it forever
View › Themes › Customize current theme lets you set the colour palette, fonts, default text sizes, background and border defaults for every visual type. Save current theme exports it as a .json file.

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.
11

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?

12

Practical Challenge

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.

Requirements
  • 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 NetSales column with a measure already defined → they get an implicit sum that bypasses your definition. Hide it.
  • Discount as a rate → they get a summed rate. Either hide it or band it in Power Query.
  • Region when it exists in two tables → they get an ambiguous answer. Rename both.
13

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

FolderMeasuresRationale
CoreTotal Revenue, Total Profit, Total Orders, Active CustomersThe base additive measures everything else builds on. First folder alphabetically and conceptually
RatiosProfit Margin %, Average Order Value, Discount RateNon-additive measures grouped together, which also serves as a quiet reminder that they behave differently
TimeRevenue YoY %, Revenue YTD, Revenue Prior YearTime-intelligence measures, all of which depend on the date table
_InternalAny helper measures not meant for direct useThe 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

HiddenReason
All *Key columns in both fact and dimensionsDragging 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 → Customer Region and Store Region
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.
The principle behind all of it
A good model makes the obvious action the correct action. Every decision above is an application of that: if a field can be misused by someone acting reasonably, either hide it, rename it, or fix it at model level so misuse becomes impossible.

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.
14

Lesson Summary

Key takeaways
  • 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 _Measures table 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

Fields / Data paneField iconsFormattingFormat pane structure
15

Progress

Marking a lesson complete stores your progress in this browser and updates your BitWithBite learner dashboard. Nothing is uploaded anywhere.

Lesson complete — 12% of Power BI Mastery done
Progress saved. Keep the momentum: the next lesson builds directly on this one.