Naming conventions in Power BI - Real Business Scenario

Scenario Mode

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

📋 Request: Your manager wants you to create a clear and easy-to-understand Power BI report. They ask you to follow good naming conventions for all tables, columns, and measures so that anyone can easily read and maintain the report.

📊 Data: You have sales data with columns for Date, Region, Product, Sales Amount, and Quantity Sold.

🎯 Deliverable: A Power BI report with properly named tables, columns, and measures following best naming conventions.

Sample Data

Date	Region	Product	Sales Amount	Quantity Sold
2024-01-01	North	Apples	100	10
2024-01-02	South	Bananas	150	15
2024-01-03	East	Oranges	120	12
2024-01-04	West	Apples	130	13
2024-01-05	North	Bananas	140	14
2024-01-06	South	Oranges	110	11
2024-01-07	East	Apples	160	16
2024-01-08	West	Bananas	170	17

1

Step 1: Rename the sales data table to a clear and descriptive name.

Rename table to 'SalesData'.

Expected Result

Table name changed to 'SalesData'.

2

Step 2: Rename columns to use PascalCase and clear names without spaces.

Rename columns: Date -> 'SaleDate', Region -> 'Region', Product -> 'ProductName', Sales Amount -> 'SalesAmount', Quantity Sold -> 'QuantitySold'.

Expected Result

Columns renamed to 'SaleDate', 'Region', 'ProductName', 'SalesAmount', 'QuantitySold'.

3

Step 3: Create a measure for total sales amount with a clear and consistent name.

Create measure: TotalSalesAmount = SUM(SalesData[SalesAmount])

Expected Result

Measure 'TotalSalesAmount' created showing sum of sales amounts.

4

Step 4: Create a measure for total quantity sold with a clear and consistent name.

Create measure: TotalQuantitySold = SUM(SalesData[QuantitySold])

Expected Result

Measure 'TotalQuantitySold' created showing sum of quantities sold.

5

Step 5: Use the renamed table, columns, and measures in a simple report visual.

Create a table visual with columns: SalesData[Region], SalesData[ProductName], and measures TotalSalesAmount, TotalQuantitySold.

Expected Result

Report visual shows sales by region and product with total sales and quantity.

Final Result

---------------------------------------------
| Region | ProductName | TotalSalesAmount | TotalQuantitySold |
|--------|-------------|------------------|-------------------|
| North  | Apples      | 100              | 10                |
| North  | Bananas     | 140              | 14                |
| South  | Bananas     | 150              | 15                |
| South  | Oranges     | 110              | 11                |
| East   | Oranges     | 120              | 12                |
| East   | Apples      | 160              | 16                |
| West   | Apples      | 130              | 13                |
| West   | Bananas     | 170              | 17                |
---------------------------------------------

✓Using clear and consistent naming makes the report easy to read and maintain.

✓Total sales and quantity measures provide quick insights into performance by region and product.

✓Renaming columns to PascalCase without spaces helps avoid errors and improves clarity.

Bonus Challenge

Create a naming convention document that explains your naming rules for tables, columns, and measures.

Show Hint

Include rules like using PascalCase, no spaces, descriptive names, and prefixes for measures (e.g., 'Total' for sums).

Practice

1. Why is it important to use clear and descriptive names for measures and columns in Power BI?

easy

A. It makes reports easier to understand and maintain.

B. It reduces the file size of the Power BI report.

C. It automatically improves the report's performance.

D. It hides sensitive data from users.

Solution

1. Step 1: Understand the role of naming in reports

   Clear and descriptive names help users and developers quickly understand what each measure or column represents.

2. Step 2: Recognize the impact on maintenance

   Consistent naming reduces confusion and makes updating or fixing reports easier over time.

3. Final Answer:

   It makes reports easier to understand and maintain. -> Option A

4. Quick Check:

   Clear naming = easier maintenance [OK]

Hint: Good names = easy reading and fixing [OK]

Common Mistakes:

• Thinking naming affects file size
• Assuming naming improves performance
• Believing naming hides data

2. Which of the following is the correct way to name a measure in Power BI following common naming conventions?

easy

A. TotalSales

B. mTotalSales

C. Measure_TotalSales

D. SalesTotalMeasure

Solution

1. Step 1: Identify common prefixes for measures

   Many teams use a prefix like 'm' to indicate a measure, making it easy to spot in lists.

2. Step 2: Compare options

   mTotalSales uses 'm' prefix with a clear name, which is a common and recommended practice.

3. Final Answer:

   mTotalSales -> Option B

4. Quick Check:

   Prefix 'm' = measure [OK]

Hint: Use 'm' prefix for measures to spot them fast [OK]

Common Mistakes:

• Not using any prefix for measures
• Using long or unclear prefixes
• Mixing measure and column naming styles

3. Given the following naming convention: prefix 'c' for calculated columns and 'm' for measures, what is the correct classification of cProfitMargin?

medium

A. Measure

B. Table Name

C. Calculated Column

D. Filter

Solution

1. Step 1: Analyze the prefix in the name

   The prefix 'c' indicates a calculated column according to the given convention.

2. Step 2: Confirm the rest of the name

   'ProfitMargin' is the descriptive part, so the full name 'cProfitMargin' is a calculated column.

3. Final Answer:

   Calculated Column -> Option C

4. Quick Check:

   Prefix 'c' = calculated column [OK]

Hint: Prefix 'c' means calculated column [OK]

Common Mistakes:

• Confusing 'c' prefix with measure
• Thinking it is a table name
• Assuming it is a filter

4. You see a measure named TotalSales and a calculated column named calcTotalSales. What is the main issue with these names?

medium

A. They are too long and complex.

B. The names are too short and unclear.

C. They use reserved keywords in Power BI.

D. They do not use consistent prefixes to identify their types.

Solution

1. Step 1: Check naming consistency

   The measure has no prefix, while the calculated column uses 'calc' prefix, causing inconsistency.

2. Step 2: Understand impact of inconsistency

   Inconsistent prefixes make it harder to quickly identify item types and maintain the report.

3. Final Answer:

   They do not use consistent prefixes to identify their types. -> Option D

4. Quick Check:

   Consistent prefixes = easier identification [OK]

Hint: Use consistent prefixes for all measures and columns [OK]

Common Mistakes:

• Thinking name length is the main problem
• Assuming reserved keywords are used
• Believing complexity is the issue

5. You want to create a naming convention for a Power BI project that includes tables, calculated columns, and measures. Which of the following naming schemes best follows best practices?

hard

A. tblCustomer, cCustomerAge, mTotalSales

B. CustomerTable, CustomerAgeCalc, TotalSalesMeasure

C. Customer, CustomerAge, TotalSales

D. tCustomer, calcAge, measureSales

Solution

1. Step 1: Identify prefixes for each item type

   Best practice uses clear prefixes: 'tbl' for tables, 'c' for calculated columns, 'm' for measures.

2. Step 2: Evaluate each option

   tblCustomer, cCustomerAge, mTotalSales uses these standard prefixes consistently and clearly, making it easy to identify item types.

3. Final Answer:

   tblCustomer, cCustomerAge, mTotalSales -> Option A

4. Quick Check:

   Standard prefixes = clear naming [OK]

Hint: Use 'tbl', 'c', 'm' prefixes for tables, columns, measures [OK]

Common Mistakes:

• Using inconsistent or unclear prefixes
• Not using any prefixes
• Using overly long or confusing names