1.3First visuals: tables, charts, cards
The essentials in 30 seconds
- A visual = a type + fields dragged into its wells (X/Y axis, legend, values): the mechanism never changes.
- Semiology: bars to compare, lines to evolve, card for a key figure, matrix to cross.
- Cross-filtering is native: clicking an element of a visual filters the whole page — that's what makes a report "come alive", unlike a frozen Excel chart.
Running mini-case — Zineb composes her first sales page
Zineb wants to show management the sales performance of the agri-food SME. She applies the section: she creates a KPI card with the total amount, a bar chart City on the X axis × Amount on the Y axis to compare, a line chart Date × Amount for the evolution, and a matrix Sales Rep × City × Amount to cross. She checks the aggregation (sum) of her amount, then clicks a bar of the bar chart: the whole page filters. Her page "lives" — she shows the magic of cross-filtering to management.
Standalone case for this section: it returns in the course, the diagram, the script and the 48h challenge of section 1.3.
1. A type + fields
The mechanism is constant: choose a type in the Visualizations pane, then drag the fields into its wells (X axis, Y axis, legend, values). The semiology remains classic: bars to compare, lines to evolve, KPI card for a key figure. Zineb starts with a KPI card (total amount) to open her page.
2. The kit: bar chart, line, matrix
The bar chart compares categories (City × Amount), the line chart shows an evolution (Date × Amount), the matrix is Power BI's pivot table (rows, columns, values, subtotals). Careful: a numeric field dragged as a value is aggregated automatically (sum by default) — you always check the aggregation. Zineb checks that her amount displays as a sum.
3. Cross-filtering
The magic specific to Power BI: cross-filtering. Clicking an element of a visual (a bar) filters all the other visuals of the page. It is the native interactivity that distinguishes a report from a frozen Excel chart. Zineb thinks of her pages as sets that react together to the same click.
🔎 Concrete example — 🔎 Concrete example — A page in 4 visuals
Zineb's first analysis page, interactive by nature:
Card : Total amount (KPI)
Bar chart : City (X axis), Amount (Y axis)
Line : Date (X axis), Amount (Y axis)
Matrix : Sales rep (rows) × City (columns) × Amount
→ clicking a bar filters the WHOLE page.Reading: each visual is a type + fields in the right wells — no cell to fill.
Lesson: clicking a visual filters the others: it's Power BI's native interactivity.
Section vocabulary
- Field wells
- The zones of the visual (X/Y axis, legend, values, tooltips) where you drag columns and measures.
Simple example: Zineb places City on the X axis and Amount on the Y axis.
What it is not: entering values by hand into the visual.
Reflex: one idea → one well.
- Matrix
- The equivalent of the pivot table: rows, columns, values, subtotals.
Simple example: Zineb crosses Sales rep × City × Amount.
What it is not: a simple one-dimensional chart.
Reflex: cross two dimensions → matrix.
- Card (KPI)
- The "big figure" visual: total, average — the opener of a dashboard.
Simple example: Zineb displays the total amount in a card.
What it is not: a detailed table line by line.
Reflex: a key figure → card.
- Cross-filtering
- Clicking an element of a visual filters the other visuals of the page.
Simple example: Zineb clicks a bar: the whole page filters.
What it is not: independent and frozen visuals.
Reflex: interactivity → cross-filtering.
- Implicit aggregation
- A numeric field dragged as a value is aggregated automatically (sum by default).
Simple example: Zineb checks that her amount aggregates as a sum.
What it is not: a text field, counted as "Count of".
Reflex: always check the aggregation.
In practice — In practice — The sales analysis page in 4 visuals
- On your sales data, create a card with the total amount (drag Amount alone into a Card visual), like Zineb.
- A clustered bar chart: City on the X axis, Amount on the Y axis — compare the cities.
- A line chart: Date on the X axis, Amount on the Y axis — the evolution appears.
- A matrix: Sales rep in rows, City in columns, Amount in values. Then CLICK a bar of the bar chart: the whole page filters.
Step-by-step script — Zineb's page in 5 min
1) Zineb drags Amount alone into a Card visual (KPI) on her sales. 2) She creates a clustered bar chart: City on the X axis, Amount on the Y axis. 3) Add a line chart: Date on the X axis, Amount on the Y axis. 4) Add a matrix: Sales rep in rows, City in columns, Amount in values. 5) Check that Amount is indeed in Sum, then click a bar of the bar chart: the whole page filters.
If a field displays as "Count of" instead of the sum, the column is badly typed: back to section 1.2.
Copy-paste template — my page in 4 visuals
Card : Total amount (KPI)
Bar chart : City (X axis) × Amount (Y axis) → compare
Line : Date (X axis) × Amount (Y axis) → evolve
Matrix : Sales rep × City × Amount → cross
Check : aggregation = SUM (not "Count of")
Test : click a bar → the whole page filters.Compare the cities
Zineb puts City on the X axis × Amount: the bar chart ranks the cities at a glance.
Track the evolution
Zineb plots Date × Amount: the line reveals the seasonality of agri-food sales.
Cross two axes
Zineb crosses Sales rep × City in a matrix to spot underperforming areas.
Filter with one click
Zineb clicks a city in the bar chart: the line and the matrix filter instantly.
✓ Best practices
- Choose the visual according to the intention: compare, evolve, quantify, cross.
- Check the aggregation (sum is not always the right default).
- Stay sober: native visuals cover 95% of needs.
✗ Common pitfalls
- A numeric field displayed as "Count of" (badly typed column).
- Multiplying exotic visuals at the expense of readability.
- Forgetting that each click filters the page (think in sets).
Key takeaways
- A visual = a type + fields in the right wells.
- Bars = compare, lines = evolve, card = key figure, matrix = cross.
- Cross-filtering is native: each click filters the page.
- Always check the aggregation of values.
48h challenge — apply tomorrow
Compose like Zineb a page of 4 visuals (KPI card, bar chart, line chart, matrix), check the aggregation of the amount, then prove cross-filtering: click a bar and describe what changes on the other visuals.
- I build a card, bar chart, line chart and matrix by dragging fields.
- I check the aggregation of values.
- I explain and use cross-filtering.
Frequently asked questions
My numeric field displays "Count of" instead of the sum, why?
The column is probably typed as text in Power Query (back to 1.2: typing). A well-typed column aggregates as a sum by default; otherwise, adjust the aggregation via the field's menu.
Can I add other types of visuals?
Yes: the AppSource store offers hundreds of custom visuals (the "…" button of the Visualizations pane). Stay sober: native visuals cover about 95% of professional needs.
What makes a Power BI report "come alive" (vs a frozen Excel chart)?