Power BI workflow (get data, transform, visualize, share) - Real Business Scenario

Scenario Mode

👤 Your Role: You are a business analyst at a retail company.

📋 Request: Your manager wants a report showing monthly sales and profit trends to understand business performance.

📊 Data: You have a sales data file with columns: Date, Product, Region, Sales Amount, and Profit.

🎯 Deliverable: Create a Power BI report that shows monthly sales and profit trends with clear visuals and share it with your team.

Sample Data

Date	Product	Region	Sales Amount	Profit
2024-01-05	Widget A	North	1000	200
2024-01-15	Widget B	South	1500	300
2024-02-10	Widget A	East	1200	250
2024-02-20	Widget C	West	1300	270
2024-03-05	Widget B	North	1100	220
2024-03-15	Widget C	South	1400	280
2024-04-10	Widget A	East	1600	320
2024-04-20	Widget B	West	1700	340

1

Step 1: Get data into Power BI

Open Power BI Desktop. Click 'Get Data'. Choose 'Excel' or 'CSV' depending on your file. Select the sales data file and load it.

Expected Result

Sales data is loaded into Power BI with columns Date, Product, Region, Sales Amount, and Profit.

2

Step 2: Transform data to prepare for analysis

In Power Query Editor, check data types. Change 'Date' column to Date type if needed. Close and Apply changes.

Expected Result

Data is clean and ready with correct data types.

3

Step 3: Create a new column for Month-Year

In Power BI Data view, create a new column with formula: MonthYear = FORMAT('Sales'[Date], "MMM yyyy")

Expected Result

A new column 'MonthYear' shows month and year like 'Jan 2024'.

4

Step 4: Create measures for total sales and total profit

Create measure Total Sales = SUM('Sales'[Sales Amount]) Create measure Total Profit = SUM('Sales'[Profit])

Expected Result

Measures calculate total sales and profit dynamically.

5

Step 5: Build a line chart visual for monthly sales and profit trends

Insert a Line Chart. Set Axis to 'MonthYear'. Add 'Total Sales' and 'Total Profit' as Values.

Expected Result

Line chart shows sales and profit trends over months.

6

Step 6: Format the visual for clarity

Add chart title 'Monthly Sales and Profit Trends'. Enable data labels. Use contrasting colors for sales and profit lines.

Expected Result

Chart is easy to read and understand.

7

Step 7: Publish and share the report

Click 'Publish' in Power BI Desktop. Select your workspace. Share the report link with your team via Power BI Service.

Expected Result

Team members can view the report online.

Final Result

Monthly Sales and Profit Trends

MonthYear | Sales Amount | Profit
---------------------------------
Jan 2024  | 2500         | 500
Feb 2024  | 2500         | 520
Mar 2024  | 2500         | 500
Apr 2024  | 3300         | 660

(Line chart with two lines showing sales and profit rising and falling over months)

✓Sales and profit show steady growth from January to April.

✓April has the highest sales and profit among the months.

✓Sales and profit trends move closely together, indicating consistent profit margins.

Bonus Challenge

Add a slicer to filter the report by Region so users can see trends for each region separately.

Show Hint

Use the 'Region' column in a slicer visual. Connect slicer to the line chart to filter data dynamically.

Practice

1. Which of the following is the correct order of steps in the Power BI workflow?

easy

A. Share reports, get data, transform data, visualize data

B. Get data, transform data, visualize data, share reports

C. Visualize data, get data, share reports, transform data

D. Transform data, share reports, get data, visualize data

Solution

1. Step 1: Understand the Power BI workflow steps

   The workflow starts by getting data from sources, then transforming it to clean and shape it.

2. Step 2: Follow the logical sequence to create insights

   After transforming, you visualize the data to see insights, then share reports with others.

3. Final Answer:

   Get data, transform data, visualize data, share reports -> Option B

4. Quick Check:

   Workflow order = Get, Transform, Visualize, Share [OK]

Hint: Remember: Get, Transform, Visualize, then Share [OK]

Common Mistakes:

• Mixing visualization before transforming data
• Sharing reports before creating visuals
• Starting with sharing instead of getting data

2. Which Power BI feature is used to clean and reshape data after importing it?

easy

A. Power Query Editor

B. Power BI Service

C. Power BI Visualizations

D. Power BI Dashboard

Solution

1. Step 1: Identify the tool for data transformation

   Power Query Editor is the tool inside Power BI used to clean and transform data after import.

2. Step 2: Differentiate from other features

   Power BI Service is for sharing, Visualizations are for charts, and Dashboards display visuals.

3. Final Answer:

   Power Query Editor -> Option A

4. Quick Check:

   Data transform tool = Power Query Editor [OK]

Hint: Data cleaning happens in Power Query Editor [OK]

Common Mistakes:

• Confusing Power BI Service with data transformation
• Thinking visualizations clean data
• Mixing dashboards with data import

3. After importing sales data and transforming it, you create a bar chart showing total sales by region. What is the next step to share this insight with your team?

medium

A. Transform the data again in Power Query Editor

B. Delete the report

C. Create a new data source

D. Publish the report to Power BI Service

Solution

1. Step 1: Understand the workflow after visualization

   Once the bar chart report is ready, the next step is to share it with others.

2. Step 2: Use the correct sharing method in Power BI

   Publishing the report to Power BI Service allows team members to access and view it online.

3. Final Answer:

   Publish the report to Power BI Service -> Option D

4. Quick Check:

   Sharing step = Publish report [OK]

Hint: Publish reports to share with your team [OK]

Common Mistakes:

• Trying to transform data again unnecessarily
• Creating new data sources instead of sharing
• Deleting reports instead of sharing

4. You imported data but the visuals show incorrect totals. Which step likely caused this issue?

medium

A. Creating visuals before importing data

B. Publishing the report to Power BI Service

C. Skipping data transformation in Power Query Editor

D. Sharing the report without permission

Solution

1. Step 1: Identify the cause of incorrect totals

   If data is not cleaned or transformed properly, totals can be wrong due to errors or duplicates.

2. Step 2: Recognize the role of data transformation

   Power Query Editor is where you fix data issues before visualizing; skipping it causes wrong results.

3. Final Answer:

   Skipping data transformation in Power Query Editor -> Option C

4. Quick Check:

   Incorrect totals = Skipped transform step [OK]

Hint: Always transform data before visualizing [OK]

Common Mistakes:

• Blaming publishing for data errors
• Creating visuals without data is impossible
• Confusing sharing permissions with data issues

5. You have sales data from multiple sources with different date formats. How should you handle this in Power BI to create a unified sales report?

hard

A. Use Power Query Editor to standardize date formats before creating visuals

B. Create visuals directly and fix date formats in the report view

C. Publish raw data and ask users to interpret date differences

D. Skip data transformation and only share raw data

Solution

1. Step 1: Recognize the need for consistent data

   Different date formats cause confusion and errors in reports, so standardization is needed.

2. Step 2: Apply transformation in Power Query Editor

   Power Query Editor lets you convert all dates to a single format before visualization, ensuring accuracy.

3. Step 3: Create visuals after data is clean

   Once dates are standardized, you can build reliable visuals and share meaningful reports.

4. Final Answer:

   Use Power Query Editor to standardize date formats before creating visuals -> Option A

5. Quick Check:

   Standardize dates in transform step [OK]

Hint: Fix data issues early in Power Query Editor [OK]

Common Mistakes:

• Trying to fix dates in visuals instead of data
• Sharing raw inconsistent data
• Ignoring data transformation step