Raushan woke up the next morning feeling a mix of excitement and nervousness. He had downloaded Power BI Desktop (the free version), and now it was time to see if the tool could live up to its promises.

He opened the app, and the first thing he noticed was how clean and simple everything seemed. No code, no complicated terms — just an interface that looked like a cross between Excel and a modern design tool.

The Interface Analogy Think of the Power BI canvas like a whiteboard. The Fields pane on the right is your bucket of LEGO pieces — each column of data is one brick. The Visualizations pane is your instruction manual — it shows you what shapes you can build. You pick a shape, drag some bricks onto it, and Power BI assembles the chart automatically.
  • Fields pane — your data columns, available to drag onto any visual
  • Visualizations pane — chart types: bar, line, map, pie, matrix, card, and 30+ more
  • Filters pane — apply visual-level, page-level, or report-level filters
  • Cross-filtering — clicking one visual automatically filters all others on the same page

📊 Step 1 — Connecting to Data

Raushan's first task was clear: get some data in there.

Luckily, he had a neat Excel file saved on his computer with his company's sales data. It wasn't huge — just a few columns — but it was enough to get started.

He clicked on Get Data → Excel Workbook. In seconds, the Navigator window opened, showing him all the sheets. He selected "Sales Data," clicked Load, and the data appeared in the Fields pane on the right.

No formula. No copy-paste. No formatting. The data was live inside Power BI.

🧑‍💻 Step 2 — The Fields Pane and Building Visuals

The next challenge: turning this data into something useful. Raushan could see his columns in the Fields pane:

  • Product Name
  • Region
  • Sales Amount
  • Date

He clicked the Bar Chart icon in the Visualizations pane. A blank chart appeared on the canvas. He dragged Product Name to the X-axis and Sales Amount to the Y-axis. Instantly, a bar chart appeared — each bar showing total sales per product.

Then he thought: "What about sales by region?"

He added a second visual — a Map. Dragged Region to the Location field and Sales Amount to the Bubble size field. Dots appeared on the map, sized by sales volume. Bigger dot = more sales.

📈 Step 3 — Cross-Filtering (The "Wow" Moment)

Raushan's eyes lit up when he clicked on one of the regions on the map.

The bar chart — on the other side of the canvas — updated instantly. It now showed only the products sold in that region. No filter panel. No extra steps. Just a click.

"This is better than Excel… way better!" Raushan thought.

What just happened is called cross-filtering. When you click a data point in any visual, Power BI automatically applies that selection as a filter to all other visuals on the same page. Every chart updates to show only the data that relates to your selection. It's the single feature that makes Power BI feel alive rather than static.

🔄 Step 4 — Refresh and the Live Connection

Raushan had one last question: what happens when the data changes?

He opened his Excel file, changed a few sales numbers, saved it, then came back to Power BI Desktop and clicked Refresh in the Home ribbon. Within seconds, the bar chart updated. The map dots resized. The report reflected his new data automatically — no rebuilding required.

This is the core promise of Power BI: your report is not a snapshot. It is a living view of your data. Change the source, hit refresh, and the report updates everywhere.

⚠️ 3 Mistakes First-Timers Make in Power BI Desktop
  1. Putting text fields on the Y-axis. If you drag Product Name to the Y-axis and Sales Amount to the X-axis by mistake, you get a chart sorted alphabetically by product name with no meaningful Y-axis values. Power BI expects numeric fields (measures or aggregatable numbers) on the value axis. Text fields go on the category axis.
  2. Ignoring data types after import. When Power BI imports your Excel data, it guesses data types. Sometimes it imports a Date column as Text, or a Revenue column as Whole Number instead of Decimal. Always check column data types in Power Query Editor before building visuals — a date sorted as text is alphabetical, not chronological.
  3. Building everything on one page. A single page with 12 visuals is overwhelming to stakeholders and slow to render. Power BI reports support multiple pages. Use one page per audience (Executive Summary, Sales Detail, Region Breakdown) and cross-link them with buttons or drill-through.
✅ What You Learned in Chapter 2
  • Power BI Desktop's three main panels: Fields (your data), Visualizations (your chart types), Filters (your slicers)
  • Connecting to Excel takes three clicks — Get Data → Excel → Load — and the data is live inside Power BI
  • Cross-filtering means clicking any data point instantly filters all other visuals on the page — no manual filter setup needed
  • Refresh updates all visuals from the source in seconds — no rebuilding, no copy-paste
  • Always verify data types in Power Query after import — wrong types cause wrong sort orders and wrong calculations

📝 Try It Yourself — Build Your First Sales Dashboard

Now it's your turn. Use the dummy dataset below and follow these steps:

📥 Dummy Dataset Download Sales Data (Excel) 50 rows · 2 sheets · INR sales data
  1. Connect to the Sales Data
    Open Power BI Desktop, click Get Data → Excel Workbook, and load the Sales Data sheet.
  2. Check data types in Power Query
    Before loading, open Power Query Editor and verify: Date column is Date type, Sales Amount is Decimal Number, Region and Product are Text. Fix any wrong types.
  3. Build Basic Visualisations
    • Bar Chart: Sales Amount (Y-axis) by Product Name (X-axis)
    • Map: Region (Location), Sales Amount (Bubble size)
    • Line Chart: Sales Amount (Y-axis) by Date (X-axis)
  4. Add a Slicer
    Add a Slicer visual for Region. Confirm it filters all three charts simultaneously.
  5. Test Cross-Filtering
    Click a bar on the bar chart — confirm the map and line chart update. Then click a dot on the map — confirm the bar chart and line chart update.
  6. Test Refresh
    Change a value in the Excel file, save it, click Refresh in Power BI Desktop, and confirm the chart updates.
🧠 Check Your Understanding

Q1. Raushan clicks a region on his Map visual and the Bar Chart immediately updates to show only that region's data. What Power BI feature is this, and is it on by default?

Show Answer

Cross-filtering (also called cross-highlighting). Yes — it is on by default for all visuals on the same report page. When you click a data point in Visual A, Power BI uses that selection as a filter context applied to all other visuals. You can control this behaviour per visual pair via Format → Edit interactions (choose Filter, Highlight, or None for each visual relationship).

Q2. After importing his Excel file, Raushan's line chart shows months sorted alphabetically (April, August, December…) instead of chronologically. What went wrong, and how does he fix it?

Show Answer

The Date column was imported as Text, not as a Date data type. Text values sort alphabetically.
Fix: open Power Query Editor (Home → Transform Data), select the Date column, and change the data type to Date using the data type dropdown in the column header. After closing and applying, the line chart will sort chronologically.

Q3. Raushan updates his Excel source file with last week's sales data and wants his Power BI report to reflect the changes. What must he do in Power BI Desktop, and what is the limitation of doing this in Desktop vs. the Power BI Service?

Show Answer

In Power BI Desktop: click Refresh in the Home ribbon. The report updates immediately.
Limitation: this only works while Power BI Desktop is open on his machine. It is a manual, local refresh. To get automatic, scheduled refresh (e.g., every morning at 7am without opening Desktop), Raushan must publish the report to Power BI Service and configure a scheduled refresh there — which also requires a data gateway if the Excel file is on a local or on-premises machine.

Coming Next Chapter 3: "Sharing and Collaborating" — Raushan publishes his report to Power BI Service, shares it with his team, and sets up Row-Level Security so each regional manager sees only their own data. Read Chapter 3 →