DEV Community: Maxwel Waweru

How to Publish a Power BI Report and Embed It into a Website

Maxwel Waweru — Sun, 05 Apr 2026 11:17:45 +0000

Introduction

Power BI is a business analytics service developed by Microsoft that allows users to visualize data, create interactive reports, and share insights across an organization.

Throughout this course, you have learned about Power BI queries, DAX, data modeling, joins, charts, dashboards, and reporting. Now, it is time to take your skills a step further by sharing your work with the world.

In this article, you will learn how to publish a Power BI report and embed it directly into a website. The process involves four main steps: creating a workspace, publishing your report, generating the embed code, and embedding the report on a website.

Step 1: Create a Workspace

Open your web browser and go to app.powerbi.com. Sign in.

Click Workspaces on the left navigation pane
Click Create workspace
Enter a name (e.g., Sales Report Workspace)
Click Save

This workspace acts as a container for storing your reports and dashboards.

Step 2: Upload and Publish Your Report

Open your report in Power BI Desktop.

Click Publish on the Home ribbon
Select your workspace
Click Select
Wait for the success confirmation
Open the report in Power BI Service

Your report is now available online in the Power BI Service.

Step 3: Generate the Embed Code

In Power BI Service:

Navigate to your workspace
Click the Reports tab
Click the More options (three dots)
Select Embed report → Publish to web (public)
Click Create embed code
Click Publish to confirm
Copy the iframe embed code

Note that this method makes your report publicly accessible.

Step 4: Embed the Report on a Website

Create an index.html file and add the following code:

<!DOCTYPE html>
<html>
<head><title>Power BI Report</title></head>
<body>
    <h1>Sales Dashboard</h1>
    <iframe width="100%" height="600"
        src="YOUR_EMBED_CODE_HERE"
        frameborder="0"
        allowFullScreen>
    </iframe>
</body>
</html>

Then:

Replace the src with your embed link
Open the file in a browser

The report will now display directly on your website.

Key Insights

“Publish to web” makes reports public and should not be used for sensitive data
Workspaces help organize reports and dashboards
Embedded reports update automatically when republished
i frame embedding works across most platforms
Public embedding is free but lacks security controls

For secure embedding, consider Power BI Embedded or SharePoint Online.

Conclusion

You have successfully learned how to publish a Power BI report and embed it into a website. The process involves creating a workspace, publishing your report, generating an embed code, and embedding it into your site.

Data Science vs Data Analysis vs Machine Learning.

Maxwel Waweru — Sat, 04 Apr 2026 10:27:34 +0000

``
What's the difference? (And why you've been using them wrong)

The Job Interview That Confused Me
I'll never forget my first data-related job interview.

The recruiter asked: "So, do you have experience in Data Science?"

I said yes.

Then: "What about Data Analysis?"

I said yes again.

Then: "And Machine Learning?"

I hesitated. Aren't they all the same thing?

Spoiler: They're not. But for years, I used these terms like they were interchangeable. And honestly? Most beginners do the same.

Today, I'm going to clear up this confusion once and for all – using one simple analogy you'll never forget.

The Coffee shop analogy
Imagine you run a small coffee shop.

Data Analysis (What happened?)
You look at your sales records from last month.

"We sold 500 lattes and 300 cappuccinos."

"Sales peak between 8-10 AM."

"December had 20% higher sales than November."

Data Analysis answers: What happened? and Why did it happen?

It looks at the past. It describes. It summarizes.

Machine Learning (What will happen?)
You take those same sales records and build a system that predicts the future.

"Tomorrow, we'll likely sell 45 lattes."

"Customers who buy a muffin usually also buy a cappuccino."

"If it rains, soup sales go up 30%."

Machine Learning answers: What will happen next?

It learns from past data to make predictions.

Data Science (The big picture)
You combine everything – analysis, predictions, business strategy, and technical systems – to run a better coffee shop.

You analyze past sales (Data Analysis)

You predict future demand (Machine Learning)

You decide to hire an extra barista for morning rush (Business Action)

You build a system that automatically orders milk when stock is low (Deployment)

Data Science is the entire universe. Data Analysis and Machine Learning are tools inside it.

The Side-by-Side Comparison
Let me break this down in a clear table.

Data Analysis (Descriptive & Diagnostic)
Main Question: What happened? Why?
Focus: Past and present data
Output: Reports, dashboards, charts, visualizations
Key Skills: SQL, Excel, Statistics
Complexity: Low to Medium
Machine Learning (Predictive)
Main Question: What will happen?
Focus: Future predictions, finding patterns in data
Output: Predictive models, algorithms
Key Skills: Python, Algorithms, Math
Complexity: Medium to High
Data Science (Comprehensive)
Main Question: How do we create value from data?
Focus: The entire process (collecting, cleaning, analyzing, modeling)
Output: Models + insights + systems + strategy
Key Skills: All of the above + Business strategy + Deployment (Cloud)
Complexity: High (covers everything)

Key Differences in the Data
Human involvement: High in Analysis (interpretation), Medium in Machine Learning (guided learning).
Data Types: Data analysis deals more with structured data, while Data Science often handles both structured and unstructured data

The Venn Diagram (Visual Learners, This Is For You)

Data Science sits in the middle – borrowing tools from both Data Analysis and Machine Learning, while adding business context and deployment.

Real-World Examples
Let me show you how these three play out in different jobs.

Example 1: E-commerce (Amazon)
Role What they do

Data Analyst "Last month, shoes were the top-selling category. Returns increased by 5%."

Machine Learning Engineer "I built a model that recommends products based on your browsing history."

Data Scientist "I led the project to reduce cart abandonment. We analyzed behavior, built a prediction model, deployed a 'you forgot this' email system, and measured a 10% recovery rate."

Example 2: Healthcare (Hospital)
Role What they do

Data Analyst "In Q3, patient wait times averaged 25 minutes. ER visits peaked on weekends."

Machine Learning Engineer "I created a model that predicts which patients are at high risk of readmission within 30 days."

Data Scientist "I built an early warning system for sepsis. It collects vital signs (data), predicts deterioration (ML), alerts nurses (deployment), and tracks how many lives were saved (evaluation)."

Example 3: Sports (Football Team)
Role What they do

Data Analyst "Our striker scores 70% of his goals in the second half. The team concedes most goals between minutes 30-45."

Machine Learning Engineer "I built a model that predicts injury risk based on player workload and fatigue data."

Data Scientist "I created a player recruitment system. It analyzes past transfers (analysis), predicts future performance (ML), and helps the coach decide who to sign (decision)."

Which One Should You Learn First?
This is the question everyone asks.

Start with Data Analysis if:
You're completely new to data

You work with Excel or SQL already

You want quick, practical results

You prefer reports and dashboards over code

Learning path: Excel → SQL → Statistics → Visualization

Jump to Machine Learning if:
You already know Python

You're excited about predictions and AI

You enjoy math and algorithms

You want to build models

Learning path: Python → Pandas → Scikit-learn → Basic ML algorithms

Go for Data Science if:
You want the full picture

You're aiming for a senior or leadership role

You like mixing business + tech + statistics

You want to deploy real systems

Learning path: All of the above + Deployment + Big Data tools

The Honest Truth
Here's what nobody tells you.

Job titles are messy.

Some companies call their Data Analysts "Data Scientists." Some call their ML engineers "Data Scientists." There's no police enforcing these definitions.

What matters is skills, not titles.

Can you clean messy data?

Can you find insights?

Can you build a simple prediction?

Can you explain it to a non-technical person?

Master those, and the title doesn't matter.

Quick Summary Table (Save This)
You want to... That's...

Describe what happened -Data Analysis
Understand why it happened -Data Analysis
Predict what will happen -Machine Learning
Group similar things together -Machine Learning
Clean and prepare data -Both!
Build a dashboard -Data Analysis
Deploy a model to production -Data Science
Solve a business problem with data -Data Science

Your Turn
Here's a simple exercise.

Think of a problem you care about. Could be:

Predicting which movies you'll like (ML)

Analyzing your monthly spending (Analysis)

Building a system to find cheap flights (Data Science)

Which one is it? Drop your answer in the comments.

Next Up in the Series

Upnext: Getting Started with Python for Data Science – the exact steps to set up your environment and write your first data script.

in the works:

Introduction to Jupyter Notebook

Top Free Tools Every Beginner Should Know

What is Data Cleaning and Why It Matters

Did this clear things up? Hit ❤️ if you'll never confuse these terms again.

I'm [Maxwel Waweru], writing daily beginner guides. Follow me so you don't miss tomorrow's Python setup guide!

Previously in this series:

What is Data Science? A Simple Beginner's Guide

Understanding the Data Science Lifecycle

Understanding the Data Science Lifecycle From messy data to real-world impact – a step-by-step journey

Maxwel Waweru — Fri, 03 Apr 2026 20:39:20 +0000

The 6 PM Realization
Picture this.

You've just learned what Data Science is (maybe from that previous article you read ). You're excited. You open your laptop, download a dataset, and… freeze.

Where do I even start?

Do you clean the data first? Build a model? Make a chart? Call it a day and watch Netflix?

I've been there. Most beginners think Data Science is a single leap from "I have data" to "I have answers."

It's not.

It's a journey with several clear stops along the way. And once you understand the map, the whole process becomes 10x less intimidating.

Let me walk you through it.

What is the Data Science Lifecycle?
Think of it like building a house.

You wouldn't start by painting the walls. You'd first:

Talk to the family (understand the need)

Draw a blueprint (plan)

Lay the foundation (prepare)

Build the structure (create)

Inspect the work (evaluate)

Hand over the keys (deploy)

The Data Science Lifecycle is exactly that—a structured, repeatable process for turning raw data into real value.

The 6 Stages (Your Roadmap)

Stage 1: Problem Definition (The "Why")
Before you write a single line of code, you must answer one question:

What problem are we trying to solve?

Bad question: "Let's use AI on our customer data!"

Good question: "Why are 20% of our customers leaving within the first 30 days?"

What happens here:

Talk to business stakeholders

Define success (e.g., "reduce churn by 15%")

Set clear goals

Beginner tip: A well-defined problem is 50% of the solution. Don't skip this.

Stage 2: Data Collection (The "Where")
Now you need the raw ingredients.

Where does data live?

Databases (SQL)

CSV/Excel files

APIs (Twitter, weather, etc.)

Web scraping

Surveys

Example: To understand customer churn, you might collect:

Customer demographics

Purchase history

Support ticket logs

Website activity

Beginner tip: Start with ready-made datasets from Kaggle or Google Dataset Search. Don't worry about collecting your own data yet.

Stage 3: Data Preparation (The "80%" – Seriously)
This is the least glamorous but most important stage.

Why? Real-world data is messy. Really messy.

Common problems you'll find:

Missing values (blanks)

Duplicates

Inconsistent formatting (e.g., "NY", "New York", "new york")

Outliers (a 200-year-old customer?)

Incorrect data types (dates stored as text)

What you'll do:

Clean missing data

Remove duplicates

Standardize formats

Handle outliers

Create new features (e.g., "age" from "birthdate")

Beginner tip: Spend time here. A clean dataset leads to good models. Garbage in = garbage out.

Stage 4: Modeling (The "AI" Part – Finally!)
This is what everyone thinks Data Science is.

You use algorithms to find patterns or make predictions.

Common algorithms for beginners:

Linear Regression (predicting numbers, like house prices)

Logistic Regression (predicting categories, like spam or not spam)

Decision Trees (simple if-then rules)

What happens here:

Split data into training and testing sets

Train the model on past data

Make predictions on new data

Beginner tip: Don't get lost in complex algorithms. Start with simple ones. They often work surprisingly well.

Stage 5: Evaluation (The "Did It Work?")
You've built a model. Great. But is it any good?

Questions you ask:

How accurate are the predictions?

Does it work on data it hasn't seen before?

Is it better than a random guess?

Common metrics (don't panic – they're simple):

Accuracy: What percentage did it get right?

Precision/Recall: How often is it wrong? (For fraud detection, you care more about catching fraud than being perfect)

Beginner tip: Always test on data the model hasn't seen during training. Otherwise, it's like giving a student the answer key before the exam.

Stage 6: Deployment (The "Real World")
A model on your laptop is worthless.

It needs to go where decisions are made.

What deployment looks like:

A dashboard (e.g., "Customer churn risk" updated daily)

An API (other apps can call your model)

A simple report emailed to the team

Beginner tip: For your first projects, "deployment" can mean sharing a Jupyter Notebook or creating a simple visualization. Don't overcomplicate it.

The Feedback Loop (Important!)
Notice the dashed arrow in the diagram?

Once you deploy, you learn. The model makes mistakes. Business needs change. New data arrives.

So you go back to Stage 1 and start again.

Data Science is never "done." It's a cycle of continuous improvement.

A Real-World Example
Let's walk through a quick example.

Problem: An e-commerce store wants to predict which customers will buy again next month.

Stage What Happens

Problem Definition "Increase repeat purchases by 10%"
Data Collection Purchase history, browsing behavior, email engagement
Data Preparation Remove inactive accounts, fill missing ages, standardize dates
Modeling Train a simple classification model (will buy / won't buy)
Evaluation Model predicts correctly 85% of the time
Deployment Add a "high risk of churn" badge to the internal dashboard Then: The marketing team sends special offers to high-risk customers. Repeat purchases go up. The model gets retrained with new data. The cycle continues.

Common Beginner Mistakes
Mistake What to Do Instead
Starting with modeling Start with problem definition
Skipping data cleaning Embrace it – it's 80% of the work
Testing on training data Always hold out a test set
Perfecting one stage before moving on Iterate. Go through the whole cycle quickly first, then improve
Forgetting deployment Ask early: "How will this be used?"
Your Turn
You don't need to master all 6 stages at once.

Start small. Pick a simple dataset. Go through each stage – even if it's messy. You'll learn more from one full cycle than from ten tutorials.

Next step: Tomorrow, we'll compare Data Science vs Data Analysis vs Machine Learning – so you never mix them up again.

Quick Recap
The Data Science Lifecycle is a structured process, not random hacking

6 stages: Problem → Collect → Prepare → Model → Evaluate → Deploy

Data preparation takes 80% of the time (and that's normal)

Modeling is just one piece of the puzzle

The cycle never ends – you continuously improve

Found this helpful? Hit the ❤️ or 🦄 to help other beginners find their way.

Question for you: Which stage sounds most intimidating to you right now? Drop a comment below – I'd love to help.

I'm [Maxwel Waweru], writing daily beginner guides on data science, analytics, and AI. Follow me so you don't miss tomorrow's post!

Previously in this series: What is Data Science? A Simple Beginner's Guide
Coming up: Data Science و Data Analysis و Machine Learning

What is Data Science? A Simple Beginner’s Guide

Maxwel Waweru — Tue, 31 Mar 2026 19:34:20 +0000

The 3 AM Confession

Let me tell you a secret.

When I first started learning to code, I thought Data Science was magic. I pictured a hooded figure in a dark room, lines of green code scrolling down a screen, whispering incantations like pandas.DataFrame() and fit_transform().

I thought you had to be a mathematician, a statistician, and a senior developer all rolled into one.

The truth? Data Science is not magic. It is storytelling.

If you are a developer looking to dip your toes into this field, or a complete beginner wondering where to start, forget the complex math for a second. Let’s strip away the buzzwords and look at what Data Science actually is.

1. The Recipe Analogy (The Easiest Way to Understand)

Imagine you want to bake the perfect chocolate chip cookie.

· Data: You have a notebook filled with past attempts. Some cookies were burnt; some were gooey. You have notes on oven temperatures, types of chocolate, and how long you chilled the dough. This is your Raw Data.
· Data Science: You look through this notebook. You notice that every time the oven was above 375°F, the cookies burnt. But when you used dark chocolate and chilled the dough for 24 hours, they were perfect.
· The Output: You write a new recipe. You now know exactly what to do to get a perfect cookie every single time. You can even predict that if a friend uses margarine instead of butter, the cookies will spread too thin.

Data Science is exactly this process, but for business problems.

You take messy ingredients (raw data), you analyze past experiments (exploratory analysis), you find hidden patterns (machine learning), and you produce a recipe (an actionable insight or a model) that tells you what to do next.

2. Breaking Down the Buzzwords

If we look at the technical definition, Data Science sits at the intersection of three distinct worlds.

graph TD
    A[Math & Statistics] --- B(Data Science)
    B --- C[Programming & Databases]
    B --- D[Domain Expertise]

Let’s break that down in human terms:

1. Math & Statistics (The Logic)

This isn’t about solving calculus problems on a whiteboard. It’s about asking: "Is this pattern real, or did it happen by accident?"

· Beginner take: You need to know the difference between average (mean) and the middle value (median). You need to know how to spot a lie (bias). You don’t need a PhD to start.

2. Programming & Databases (The Toolbox)

This is where you feel at home. We use code to clean the "dirty" data and build models.

· Python is the language of choice (though R is great too).
· SQL is non-negotiable. Most data lives in databases; you have to know how to ask for it.
· Beginner take: If you can write a for loop and use SELECT * FROM, you have enough to start learning the rest.

3. Domain Expertise (The Context)

This is the secret sauce. If you are analyzing healthcare data but don’t know what "blood pressure" means, your model will fail.

· Beginner take: You don't need to be a doctor. But you must understand why the data exists. Data Science is useless without context.

The Data Science Workflow (What the Job Actually Looks Like)

Most beginners think the job is 100% building AI models. In reality, building the model is about 10% of the job. Here is the actual workflow:

Step 1: Ask the Right Question

Before writing a single line of code, you ask: "What problem are we solving?"

· Bad question: "How do we use AI?"
· Good question: "Why are we losing customers in the first month?"

Step 2: Data Collection & Cleaning (The 80% Rule)

If you take one thing away from this article, let it be this: Data Scientists spend 80% of their time cleaning data.

· You will find missing values (NaN).
· You will find duplicates.
· You will find dates formatted as text.
· Your job here is to turn chaos into a tidy table.

Step 3: Exploration (EDA)

You play with the data. You make charts.

· Does more screen time correlate with lower test scores? (Plot a scatter plot).
· Which product sells the most? (Plot a bar chart).
This is where you find the "story."

Step 4: Modeling (The "AI" Part)

This is where you use algorithms (like Linear Regression, Random Forests, or Neural Networks) to make predictions.

· Example: Based on past data, this customer will probably cancel their subscription next week.

Step 5: Deployment & Communication

If you build a model that stays on your laptop, it is useless. You have to deploy it (put it in the cloud) or create a dashboard. Most importantly, you have to explain to the CEO why they should listen to your model.

4. Common Myths (Let’s Clear the Air)

Myth Reality
You need to be a genius at math. You need to be curious. Basic statistics and logical thinking get you 90% of the way. The libraries (scikit-learn) do the heavy math for you.
You need a PhD. Some research roles do, but most industry roles care about your portfolio. Can you solve problems? That’s what matters.
Data Science is just about AI. No. Most Data Science is about descriptive analytics. "What happened last quarter and why?" AI is just a small (but fun) subset.
It’s a solo job. It’s incredibly collaborative. You work with engineers, product managers, and business leaders constantly.

5. How to Start (Without Overwhelming Yourself)

If you want to transition into Data Science, don’t try to learn everything at once. Do this instead:

Learn Python Basics: If you already know JavaScript or Java, Python will feel like writing English. Focus on pandas (for data) and matplotlib (for charts).
Master SQL: Go to W3Schools or LeetCode and practice SQL until you can join tables in your sleep.
Do a "Full" Project: Don’t just follow a tutorial. Find a dataset on Kaggle (e.g., Titanic or Housing Prices). Try to predict something. · Fail. · Google the error. · Fix it. · This is the real learning loop.
Share Your Work: Write a post on Dev.to showing your first chart. Put the code on GitHub. This builds your portfolio faster than any certificate.

Conclusion

Data Science is not about having a crystal ball.

It is about taking the messiest parts of a business (or a kitchen), using code to clean it up, using statistics to find the truth, and using storytelling to get people to act on it.

You don't have to know everything today. You just have to ask one question: "I wonder why that happens?"

If you have that curiosity, you already have the hardest skill to teach. The code is just the tool you use to find the answer.

Ready to take the next step?
Drop a comment below if you want a follow-up post on "Understanding the data Science lifecycle"

I’m Maxwel Waweru, a Data Scientist who believes in breaking down complex topics into simple stories. Follow me for more.

UNDERSTANDING DATA MODELING IN POWER BI:JOINS,RELATIONSHIPS AND SCHEMAS EXPLAINED

Maxwel Waweru — Tue, 31 Mar 2026 18:28:06 +0000

A beautiful report is only as good as the data model behind it,
in this modern world of Business Intelligence. Power BI is a powerful tool, but without a solid understanding of how tables connect, you’ll quickly run into incorrect totals, sluggish performance, and confusing filter behavior.

This article serves as your complete guide to mastering data modeling in Power BI. We will break down the technicalities of SQL joins, explain the unique nature of Power BI relationships, explore star schemas, and walk through where to actually build these elements inside the Power BI interface.

1. What is Data Modeling?

Data modeling is the process of defining how data tables connect to each other. It involves structuring raw data (often from multiple sources) into a logical, unified framework that is optimized for reporting.

A good data model ensures that:

· Accuracy: Filters propagate correctly to show the right numbers.
· Performance: Reports load quickly (compression and optimized queries).
· Usability: End-users can intuitively click through reports without encountering errors.

2. SQL Joins Explained (The Foundation)

Before we look at Power BI Relationships, we must understand Joins. Joins occur in the Power Query Editor (the "Get Data" phase). They combine two tables horizontally based on a matching column, resulting in a single flattened table.

Here are the six essential SQL joins, visualized and explained with a real-world example of Sales and Customers.

The Setup

· Sales Table: Contains SaleID, CustomerID, and Amount.
· Customers Table: Contains CustomerID and CustomerName.

1. INNER JOIN

Returns only rows where there is a match in both tables.

· Use Case: Finding sales that belong to existing, valid customers. If a sale has a CustomerID not found in the Customers table, it is excluded.

[Sales] ---(Match)---> [Customers]
Result: Only Sales associated with a known Customer.

2. LEFT JOIN (LEFT OUTER)

Returns all rows from the left table (Sales) and the matched rows from the right table (Customers). If no match, results are null.

· Use Case: Keeping all sales transactions, even if the customer record was deleted or the ID is missing. This is the most common join in Power Query to preserve fact data.

[Sales] ---------------------> [Customers]
Result: All Sales. Customer Name appears if exists; otherwise, blank.

3. RIGHT JOIN (RIGHT OUTER)

Returns all rows from the right table (Customers) and the matched rows from the left table (Sales). This is the logical opposite of a LEFT JOIN.

· Use Case: Finding all customers, regardless of whether they have made a purchase.

[Sales] <--------------------- [Customers]
Result: All Customers. Sales data appears only if they bought something.

4. FULL OUTER JOIN

Returns all rows from both tables. Where there is a match, they are combined; where there is not, missing sides are filled with null.

· Use Case: Merging two systems to see a complete master list, such as merging legacy CRM data with a new CRM to see all records.

[Sales] <----------------------> [Customers]
Result: Every sale and every customer. Unmatched sales have null names; unmatched customers have null amounts.

5. LEFT ANTI JOIN

Returns only rows from the left table that have no match in the right table.

· Use Case: Data cleansing. Finding orphaned records (sales with missing Customer IDs) to flag or delete them.

[Sales] ---(No Match)---> [Customers]
Result: Only sales with invalid CustomerIDs.

6. RIGHT ANTI JOIN

Returns only rows from the right table that have no match in the left table.

· Use Case: Finding inactive customers (customers who exist in the CRM but have never made a sale).

[Sales] <---(No Match)--- [Customers]
Result: Customers with zero sales.

3. Power BI Relationships vs. SQL Joins

This is the most critical distinction to understand. Do not confuse a SQL Join with a Power BI Relationship.

Feature SQL Join (Power Query) Power BI Relationship (Model View)
Result Creates a single new table. Tables remain separate but connected.
Storage Data is duplicated (denormalized). Increases file size. Data is stored once (normalized). Optimizes compression.
Filtering No dynamic filtering. It’s a static merge. Dynamic. Filters flow across tables automatically based on the relationship.
Best For Lookup operations, adding columns to fact tables, or final staging. Creating star schemas, row-level security, and complex calculations (DAX).

Rule of Thumb: Use Joins in Power Query to bring attributes into a table (e.g., adding "Product Name" to the Sales table). Use Relationships in the Model View to connect dimensions to facts.

4. Power BI Relationships Deep Dive

Relationships are the glue of the data model. You define them in the Model View.

Cardinality

· One-to-Many (1:M): The most common. A single row in one table (e.g., Products) relates to many rows in another (e.g., Sales). The filter flows from the "One" side to the "Many" side.
· One-to-One (1:1): Rare. Used for splitting a wide table for security purposes or when using "Bidirectional" cross-filtering.
· Many-to-Many (M:M): Complex. Either both tables have duplicate values, or a bridging table is involved. Power BI now supports M:M relationships natively, but they require careful management to avoid performance hits.

Cross-Filter Direction

· Single: The default. Filters propagate from the "One" side to the "Many" side.
· Both (Bidirectional): Allows filtering in both directions. Useful for row-level security or bridging tables, but overuse can create ambiguous filter paths (circular dependencies).

Active vs. Inactive Relationships

You can only have one active path of propagation between two tables at a time.

· Active: Solid line. Used by default for filters.
· Inactive: Dotted line. Not used by default. You must activate it in DAX using the USERELATIONSHIP() function.
· Use Case: A "Sales" table might have an active relationship to the "Order Date" table, but an inactive relationship to the "Ship Date" table to calculate shipping delays.

5. Fact vs. Dimension Tables

A proper model relies on distinguishing these two types of tables.

· Fact Tables (Transactions):
· Contains quantitative data (numbers, measures).
· Think: Sales Amount, Quantity, Revenue.
· Usually long and narrow (many rows, few columns).
· Changes frequently (every transaction).
· Dimension Tables (Descriptions):
· Contains descriptive data (text, attributes).
· Think: Customer Name, Product Category, Date.
· Usually short and wide (few rows, many columns).
· Changes slowly (e.g., a customer changes address).

6. Data Schemas: Star, Snowflake, and Flat Table

How you arrange your Facts and Dimensions defines your schema.

1. Star Schema

The gold standard for Power BI.

· Structure: A central Fact table surrounded directly by Dimension tables.
· Look: Like a star.
· Advantages: Optimal for Power BI VertiPaq engine; fastest performance; simplest for DAX calculations.

        [Customer]
            |
[Product] — [Sales] — [Date]
            |
        [Store]

2. Snowflake Schema

· Structure: Dimensions are normalized. For example, Product table links to Subcategory, which links to Category.
· Disadvantage: Increases the number of tables; can slow down performance compared to Star; more complex to navigate.
· When to use: Rarely in Power BI. Only use if the source data is strictly structured this way and flattening it in Power Query is too complex.

3. Flat Table (Denormalized / DLAT)

· Structure: A single table containing both facts and dimensions (e.g., Date, Product, Sales all in one row).
· Advantage: Simple for beginners; no relationships to set up.
· Disadvantage: Massive file size (high duplication); difficult to maintain; limited analytical complexity (time intelligence becomes hard). Avoid this unless your data is very small and static.

7. Advanced Concepts & Common Issues

Role-Playing Dimensions

A single dimension table used to filter multiple columns in a fact table.

· Example: A Date dimension used to filter Order Date, Ship Date, and Delivery Date.
· Implementation: You cannot have three active relationships to the same table. Keep one active (e.g., Order Date) and use USERELATIONSHIP in DAX for the others.

Common Modeling Issues

1. Ambiguity: Creating bidirectional relationships that create multiple paths between tables. Power BI will throw a warning. Resolve by using single direction or bridging tables.
2. Many-to-Many Ambiguity: Having two M:M relationships leads to inconsistent totals. Use a bridge/concordance table instead.
3. Referential Integrity: Having sales rows with CustomerID = Null that break the relationship. Either fix the data source or use a "No Match" row in the dimension table.

8. Step-by-Step: Where to Build This in Power BI

A. Creating Joins (Power Query Editor)

Go to Home > Transform Data.
In the Power Query Editor, select the table you want to merge into (e.g., Sales).
Click Home > Merge Queries.
Select the second table (e.g., Customers).
Select the matching columns (e.g., CustomerID).
Choose the Join Kind (Inner, Left Outer, etc.).
Click OK. Expand the new column to bring in the data (e.g., CustomerName).

B. Creating Relationships (Model View)

Click the Model View icon on the left side of the screen.
Drag and Drop: Click the column in the Dimension table (e.g., Products[ProductID]) and drag it to the column in the Fact table (e.g., Sales[ProductID]).
Manage Relationships: · Go to Modeling > Manage Relationships. · Click New. · Select the two tables and columns. · Set Cardinality (e.g., Many to One) and Cross Filter Direction (Single).

C. Managing Inactive Relationships

In Model View, double-click the line between two tables.
Uncheck "Make this relationship active."
To use it in a measure:

   Sales by Ship Date = 
   CALCULATE(
       SUM(Sales[Amount]),
       USERELATIONSHIP(Sales[ShipDateKey], Date[DateKey])
   )

Conclusion

Mastering data modeling is the line between a Power BI user and a Power BI professional. Remember the hierarchy:

Structure: Use Joins in Power Query to shape your data and add necessary attributes.
Connect: Use Relationships in Model View to define business logic.
Optimize: Aim for a Star Schema with One-to-Many relationships flowing from Dimensions to Facts.

By understanding the difference between a static SQL join and a dynamic Power BI relationship, and by properly designing your fact and dimension tables, you will build models that are fast, accurate, and scalable.

HOW EXCEL IS USED IN REAL-WORLD DATA ANALYSIS

Maxwel Waweru — Sun, 29 Mar 2026 18:26:25 +0000

When people hear data analysis, they often imagine complex Python scripts, SQL queries, or advanced BI tools. However, in reality, the foundation of data analysis across most organizations—from global corporations to local startups—is Microsoft Excel.

If you're starting your journey into data, Excel is not optional—it is a core skill required across operations, finance, marketing, and analytics roles.

In this article, I’ll explain how Excel is used in real-world scenarios using a product performance dataset from Jumia, one of Africa’s largest e-commerce platforms.

what is excel

Microsoft Excel is far more than a spreadsheet tool. It is a multi-functional analytical platform that serves as:

A database – storing large volumes of structured data

A calculation engine – performing simple to complex computations

A data transformation tool – cleaning and reshaping messy datasets

A visualization platform – building dashboards and reports

Real-World Applications of Excel

1.Marketing

: Evaluating Pricing Strategy
A marketing team needs to determine whether discounts drive engagement.

Task: Analyze the relationship between discount percentage and customer reviews

Solution: Using PivotTables and scatter plots to identify trends.

Insight: Moderate-to-high discounts significantly increased customer engagement.

2. Merchandising

: Identifying Underperforming Products
The goal is to flag products that are discounted but poorly rated.

Task: Detect products with high discounts and low ratings

Solution: Conditional Formatting to highlight risk products instantly

3. Operations

: Data Cleaning
Raw data is rarely usable in its original form.

Task: Convert text-based values into numeric format

Solution:

Find & Replace to clean currency values

TEXTSPLIT to extract ratings

Key Excel Features Used

1. Data Cleaning
Removed “KSh” and commas from price fields

Extracted numeric ratings using TEXTSPLIT

Used ABS() to correct negative values

2. Calculated Columns
Discount Amount = Old Price – Current Price

Rating Classification using nested IF statements

Discount categorization (Low, Medium, High)

3. PivotTables
Used to summarize:

Average ratings by discount category

Discount distribution across products

4. XLOOKUP
Used to map:

Top-performing products

Associated prices and names

5. Conditional Formatting
Highlighted:

High-discount, low-rating products

Immediate visual alerts for decision-making

6. Dashboard Creation
Built an interactive dashboard with:

Charts linked to PivotTables

Slicers for filtering data dynamically

Scatter plots to reveal pricing patterns

Key Insights from the Analysis
Discounts increase engagement: High-discount products generated significantly more reviews

Discounts don’t guarantee quality: Some heavily discounted products had poor ratings

Optimal pricing range: Products discounted between 20–40% achieved the highest ratings

Strong customer satisfaction: Majority of products had ratings above 4.5

The Excel Mindset
Effective Excel usage goes beyond formulas:

Maintain a clean workflow (Raw → Working → Dashboard)

Use Excel Tables for dynamic updates

Document formulas for future reference

Focus on clarity and reproducibility

Conclusion
Excel remains one of the most powerful and accessible tools for data analysis. It bridges the gap between raw data and actionable business insights.

From cleaning messy datasets to building dashboards and uncovering trends, Excel enables end-to-end analysis without requiring advanced programming skills.

For anyone entering data-related fields, mastering Excel is one of the highest ROI skills you can develop.