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

Data View & Model View

24 min 5 quiz questions 1 practical challenge 3 syllabus topics

Report view gets the attention, but the two views behind it are where correctness lives. Data view is your validation surface — the place you confirm what actually loaded. Model view is where relationships are made and broken. This lesson makes both of them familiar.

Lesson 8 of 72 · Power BI Desktop 11%
01

Learning Objective

Most people build reports without ever looking at Data view or Model view properly, and then cannot explain why a number is wrong. These two views are where the answers are.

By the end of this lesson you will be able to
  • Use Data view to validate a load and inspect actual row values
  • Set column properties — data type, format, summarization, sort-by column, data category
  • Read a Model view diagram: tables, relationship lines, cardinality and filter direction
  • Explain why Data view is missing on a DirectQuery-only model
  • Organise a model with display folders, hidden fields and layouts
02

Why This Matters

A concrete scenario. Your monthly revenue chart shows the months in alphabetical order: April, August, December, February… It looks absurd and there is no obvious fix in the chart.

The fix is not in Report view at all. It is a Sort by column property set in Data view, telling Power BI to order MonthShort by MonthNumber. People lose genuine hours to this because they look for the answer where the symptom is.

Similarly: a map visual that plots everything in the wrong country is almost always a missing Data category — another Data view property. And a measure that returns blank when sliced is almost always a relationship problem, visible only in Model view.

The pattern worth internalising
Symptoms appear in Report view. Causes usually live in Data view or Model view. When something is wrong with a visual, resist fiddling with the visual. Ask which of the other two views owns the underlying property.
03

Concept

Data view

Data view (labelled Table view in recent releases) shows the loaded rows of one table at a time, as a grid. It is the closest thing Power BI has to opening the data in Excel.

What you use it for

  • Validating a load. The status bar at the bottom shows the row count. Compare it against the source. This is the single most valuable thing in this view.
  • Looking at actual values. When a measure returns something odd, seeing real rows often makes the cause obvious immediately.
  • Setting column properties. Select a column and the Column tools contextual tab appears.
  • Checking a calculated column. Unlike measures, calculated columns are materialised per row and you can see their values here.

Column tools — the five properties that matter

Column properties and what they fix
PropertyWhat it doesThe problem it solves
Data typeText, Whole number, Decimal, Date, True/False, etc.Numbers stored as text will not aggregate; dates as text break time intelligence
FormatHow the value is displayed — currency, decimals, date format, percentageSet it here once and every visual inherits it, instead of formatting each visual separately
SummarizationDefault aggregation, or Don't summarizeStops Power BI summing numeric dimensions like Year, scores and ID numbers
Sort by columnOrders this column by the values of anotherThe alphabetical-months problem. Sort MonthShort by MonthNumber
Data categoryMarks a column as Address, City, Country, Postal code, Web URL, Image URL…Tells map visuals how to geocode; makes URL columns clickable and image URLs render
Sort by column has one rule people trip over
The sort-by column must have a one-to-one relationship with the column being sorted within the table. Every distinct MonthShort value must map to exactly one MonthNumber. If "Jan" mapped to both 1 and 13, Power BI refuses with a circular-dependency error. This is why you sort month names by month number, not by date.
Data view does not appear when every table in the model uses DirectQuery, because no rows are imported for it to show. If the view switcher only offers two icons, that is why — it is not a fault. Composite models with at least one imported table do show it.

Model view

Model view shows your tables as boxes and your relationships as lines. It is a diagram, and it is also the editor — you create relationships by dragging between columns.

Reading a relationship line

What the line tells you
FeatureMeaning
Solid lineActive relationship — filters flow along it automatically
Dashed lineInactive relationship — exists but only used via USERELATIONSHIP in DAX
1 and * at the endsCardinality. 1 on the dimension side, * (many) on the fact side
Single arrow mid-lineFilter flows one way — from the 1 side to the many side
Double arrowBidirectional filtering. Powerful and a common source of trouble
No line at allNo relationship. Slicing across these tables will not work

Module 4 covers cardinality and filter direction properly. For now, the point is that all of this information is readable at a glance from the diagram — and that reading it is the fastest way to diagnose a class of problems that look mysterious from Report view.

Organising the model

Model view is also where you make a model pleasant to use:

  • Hide in report view. Right-click any field. Hidden fields still work in DAX and relationships; they simply stop cluttering the Data pane for report authors. Key columns and raw fact columns should almost always be hidden.
  • Display folders. Group related measures in the Properties panel. A model with thirty measures becomes navigable with four folders.
  • Layouts. Create additional diagram tabs showing a subset of tables. On a twenty-table model this is the difference between a readable diagram and spaghetti.
  • Descriptions. Add one to any field in the Properties panel. It surfaces as a tooltip in the Data pane — the cheapest documentation available.
04

Visual Explanation

A star schema as Model view renders it. Select any table to inspect it.

Two things a reviewer would notice in that model
First, Region exists in both Customer and Store. That is legitimate but ambiguous — a visual sliced by "Region" must be explicit about which one, and the two will give different answers. Rename them Customer Region and Store Region.

Second, ShipDate and OrderDate both point at the date table, so only one relationship can be active. That is the role-playing dimension problem, and Module 4 Lesson 5 solves it.
05

Power BI Demonstration

Validate a load in Data view
Switch to Table view. Select your table in the Data pane. Read the row count in the status bar at the bottom and compare it to the source file.
Fix an alphabetically-sorted month
Select the MonthShort column → Column tools › Sort by column › MonthNumber. Return to Report view and the axis is now in calendar order.
Stop a numeric dimension summing
Select Year → Column tools › Summarization › Don't summarize.
Set a format once, inherit everywhere
Select NetSales → Column tools › Format › Currency, 2 decimals. Every visual using it now formats correctly without per-visual work.
Set a data category for mapping
If you have a country or city column, select it → Column tools › Data category › Country/Region. Map visuals geocode far more reliably with this set.
Read the model diagram
Switch to Model view. For each relationship line, note whether it is solid or dashed, where the 1 and the * sit, and which way the arrow points.
Hide the clutter
Right-click every key column (CustomerKey, ProductKey, StoreKey) → Hide in report view. Report authors never need to see them.
Add a display folder
Select a measure, and in the Properties panel type a folder name under Display folder. Do it for several measures with the same folder name and they group together in the Data pane.
Add a description
With a measure selected, fill in Description in Properties. Hover the field in the Data pane and your text appears as a tooltip — self-documenting models cost almost nothing.
Create a second layout
In Model view, click the + beside the layout tabs at the bottom. Drag in only the tables relevant to one subject area. Large models become readable.
Table viewselect columnColumn toolsSort by column
06

Example Dataset

Load this alongside the sales file if you want to practise the sort-by-column and summarization fixes on a real date table. You will build your own in Module 4, but having one now makes this lesson's exercises concrete.

bwb-date-table.csv
47 KB · 731 rows · 14 columns · CSV
Business context
A complete, gap-free date table covering 2024–2025 with calendar and fiscal attributes. Provided as a reference so you can compare it against the one you build yourself in DAX or Power Query — building your own is the better habit.

Columns & data types

ColumnData typeMeaning
DateDateOne row per day, no gaps. This is the key column.
YearWhole numberCalendar year.
MonthNumberWhole number1–12. Use this to sort MonthShort correctly.
MonthShortTextJan, Feb, Mar … Needs Sort By Column set to MonthNumber.
MonthNameTextFull month name.
QuarterNumberWhole number1–4.
QuarterTextQ1–Q4.
WeekOfYearWhole numberISO week number.
DayNameTextMonday … Sunday.
DayOfWeekWhole number1 = Monday. Sort key for DayName.
IsWeekendTextYes / No flag.
YearMonthTextYYYY-MM, handy for a continuous month axis.
FiscalYearWhole numberFiscal year starting 1 July.
FiscalMonthWhole number1–12 where 1 = July.

Questions this dataset can answer

  • How does a fiscal-year view change the picture versus calendar year?
  • Which weekday generates the most revenue?
07

Step-by-Step Exercise

Load the date table
Get data → Text/CSV → bwb-date-table.csv → Transform Data → Close & Apply.
Validate it
In Table view, confirm 731 rows — that is 366 + 365 for 2024 and 2025. A date table with gaps breaks time intelligence silently, so this check matters.
Build a broken month chart
In Report view, make a bar chart with MonthShort on the axis. Note the alphabetical order.
Fix it in Data view
Set MonthShort to sort by MonthNumber. Return and confirm.
Find every column that should not summarize
Go through the date table and set Don't summarize on Year, MonthNumber, QuarterNumber, WeekOfYear, DayOfWeek, FiscalYear and FiscalMonth.
Sort DayName correctly too
Set DayName to sort by DayOfWeek. Confirm a weekday chart now runs Monday to Sunday.
Relate it to Sales
In Model view, drag Date[Date] onto Sales[OrderDate]. Note the cardinality and direction Power BI chose.
Check what happened to ShipDate
Try dragging Date[Date] onto Sales[ShipDate] as well. Power BI creates it but makes it inactive (dashed). Note this and move on — Module 4 explains it.
08

Expected Result

Checks
CheckExpected
Date table row count731
MonthShort chart orderJan, Feb, Mar … Dec
DayName chart orderMonday … Sunday
Year in a cardBlank or the year — not 4,049
Date → Sales[OrderDate] relationshipSolid line, 1 on Date, * on Sales, arrow pointing to Sales
Date → Sales[ShipDate] relationshipDashed line — inactive
Why the second relationship is inactive
Power BI permits only one active relationship path between any two tables. Since OrderDate already provides one, ShipDate's is created inactive. This is not a bug — it is the engine preventing ambiguity about which date a measure should filter on. Module 4 Lesson 5 covers the two ways to work with it: role-playing dimension copies, or USERELATIONSHIP.
09

Common Mistakes

Trying to fix sort order in the visual
Right-clicking a chart and using "Sort axis" only sorts by value or by the label alphabetically. It cannot produce calendar order for month names.

Fix: Set Sort by column on the column itself, in Data view. Fix it once at model level and every visual inherits it.
Formatting numbers on each visual separately
Setting currency and decimals in each visual's Format pane. Tedious, and the moment you add a new visual it is inconsistent again.

Fix: Set Format on the column or measure once, in Column tools or Measure tools. Every visual inherits it automatically.
Assuming Data view is missing means something is broken
On a pure DirectQuery model there are no imported rows, so the view does not appear. People assume a corrupted install.

Fix: Check your storage mode. If everything is DirectQuery, this is expected behaviour.
Leaving key columns visible in the Data pane
Report authors see CustomerKey, ProductKey and every raw fact column, and inevitably use one of them by mistake.

Fix: Hide every key column and every raw fact column once measures exist. A clean Data pane is one of the clearest signals of a well-built model.
Ignoring ambiguous column names across tables
Region exists in both Customer and Store. Two visuals sliced by "Region" give different answers and nobody can see why.

Fix: Rename them to be unambiguous — Customer Region, Store Region. Do it in Power Query or in the model, but do it.
10

Professional Tip

Build a validation page in Data view's terms
Create a report page called _Validation (the underscore sorts it first) and hide it. On it, put cards showing:

• COUNTROWS of each table
• MIN and MAX of your main date column
• SUM of your primary measure with no filters
• DISTINCTCOUNT of each key column

Every time you refresh, glance at this page. If a number moves unexpectedly, you know immediately — before anyone else sees a wrong figure. This takes ten minutes to build and is the single most useful defensive habit in Power BI.

One more: add a description to every measure as you write it. The Properties panel field takes ten seconds and surfaces as a hover tooltip in the Data pane. It is the only documentation that lives where people will actually see it.

11

Knowledge Check

Knowledge Check

5 questions. Answer each one to see why the right answer is right.

Your month names sort alphabetically on a chart axis. Where is the fix?

A relationship line in Model view is dashed rather than solid. What does that mean?

The Table (Data) view icon is missing from the view switcher. What is the most likely reason?

Why does hiding key columns from report view improve a model?

You set Format to Currency on the NetSales column. What happens?

12

Practical Challenge

Practical Challenge

Audit and clean up a model

Load bwb-retail-sales.csv, bwb-products.csv, bwb-customers.csv, bwb-stores.csv and bwb-date-table.csv. Then perform a model audit using only Data view and Model view, and produce a written list of every problem you find with its fix.

Requirements
  • Verify the row count of every table against its source file
  • Find every numeric column that should not summarize and fix it
  • Find every text column that needs a sort-by column and fix it
  • Identify every ambiguous column name that appears in more than one table
  • List every column you would hide from report view, with a reason
  • Note the relationship state for each pair of tables, including any inactive ones

Work table by table, and for each column ask three questions:

  1. Is it numeric but categorical? → Don't summarize
  2. Is it text with an inherent order that is not alphabetical? → Sort by column
  3. Is it a key, or a raw fact column that a measure will wrap? → Hide

For ambiguity, list every column name across all five tables and look for duplicates. Two are obvious; one is easy to miss.

13

Solution

Try the challenge properly before opening this. Reading a solution you have not attempted feels like learning, but it is not.

The audit

1 · Row counts

TableExpected rows
Sales15,067
Products114
Customers900
Stores8
Date731

Any mismatch means Power Query dropped rows — investigate before doing anything else.

2 · Columns needing Don't summarize

  • Date table: Year, MonthNumber, QuarterNumber, WeekOfYear, DayOfWeek, FiscalYear, FiscalMonth
  • Stores: OpenedYear
  • Sales: Discount — it is a rate. Summing discount rates across rows is meaningless. It can be averaged (weighted) or banded, never summed.

3 · Columns needing a sort-by column

  • MonthShort → sort by MonthNumber
  • MonthName → sort by MonthNumber
  • DayName → sort by DayOfWeek
  • Quarter → sort by QuarterNumber (Q1–Q4 happens to sort correctly alphabetically, but setting it explicitly protects you if the labels are ever changed to something like "Qtr 1")

4 · Ambiguous column names

NameAppears inWhy it mattersFix
RegionCustomers and StoresTwo different concepts — where the customer is, versus where the store is. A visual labelled "Region" is genuinely ambiguous and the two give different answers.Rename to Customer Region and Store Region
ProductKeySales and ProductsExpected and correct — this is the join key. Not a problem.Leave it; hide the Sales copy
YearDate table, and OpenedYear in StoresNot an exact clash, but close enough to confuse. The easy one to miss.Leave as is — the names already differ. Worth noting in documentation

5 · Columns to hide from report view

ColumnReason
Sales[CustomerKey], [ProductKey], [StoreKey]Join keys. Report authors never need them; showing them invites misuse
Products[ProductKey], Customers[CustomerKey], Stores[StoreKey]Same reason on the dimension side
Sales[NetSales], [COGS], [Profit], [Quantity]Hide these once measures exist. Until then you need them. After that, hiding them forces everyone through your defined measures rather than an implicit sum
Sales[UnitPrice]Duplicated from the product dimension at transaction time. Keeping it visible invites someone to average it, which is a weighted-average trap
Date[MonthNumber], [DayOfWeek], [QuarterNumber]Sort-by helper columns. They must exist, but nobody should put them on a chart

6 · Relationship state

FromToState
Date[Date]Sales[OrderDate]Active (solid), 1 to *, single direction
Date[Date]Sales[ShipDate]Inactive (dashed) — only one active path allowed
Products[ProductKey]Sales[ProductKey]Active, 1 to *, single direction
Customers[CustomerKey]Sales[CustomerKey]Active, 1 to *, single direction
Stores[StoreKey]Sales[StoreKey]Active, 1 to *, single direction — but note that most Sales rows have a blank StoreKey, which lands them in a blank row on the Stores side
The observation that separates a good audit from a checklist
The Region ambiguity is the finding that matters most here, and it is the one least likely to be caught by a mechanical pass. It will not produce an error. It will produce two visuals labelled "Revenue by Region" that show different numbers, and a stakeholder who concludes the report cannot be trusted.

Modelling problems that produce plausible disagreement rather than visible breakage are the ones worth hunting for deliberately — which is the same lesson as the detectability ranking from Lesson 2.
14

Lesson Summary

Key takeaways
  • Data view validates loads (row count in the status bar), shows real values, and hosts column properties.
  • The five column properties that matter: data type, format, summarization, sort-by column, data category.
  • Sort by column fixes alphabetical months. The sort-by column must map one-to-one with the column being sorted.
  • Model view shows tables and relationships. Solid = active, dashed = inactive; 1 and * show cardinality; the arrow shows filter direction.
  • Only one active relationship path is allowed between two tables — which is why a second date relationship arrives inactive.
  • Hide keys and raw fact columns once measures exist. Hidden fields still work in DAX and relationships.
  • Data view is absent on pure DirectQuery models — that is expected, not a fault.
  • Build a hidden validation page with row counts, date ranges and unfiltered totals. It is the cheapest defence against silent breakage.

Syllabus topics delivered

Data / Table ViewModel ViewReading the model diagram
15

Progress

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

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