Naming conventions in Power BI - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a measure with a proper name.

Power BI

Total Sales = SUM([1][SalesAmount])

Drag options to blanks, or click blank then click option'

A1Sales

Bsales

CSales

DTotal-Sales

Attempts:

3 left

💡 Hint

Common Mistakes

Starting names with numbers

Using special characters like '-'

Using lowercase when uppercase is standard for table names

The measure name should start with a letter and avoid special characters. 'Sales' is a valid table name.

2fill in blank

medium

Complete the code to follow naming conventions for calculated columns.

Power BI

Profit Margin = DIVIDE([1][Profit], [1][SalesAmount])

Drag options to blanks, or click blank then click option'

Asales

BSales-Data

C1Sales

DSales

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase table names

Starting table names with numbers

Including special characters in names

Table names should be capitalized and not start with numbers or contain special characters. 'Sales' is correct.

3fill in blank

hard

Fix the error in the measure name to follow naming conventions.

Power BI

[1] = SUM(Sales[Units])

Drag options to blanks, or click blank then click option'

ASales_Units

BUnits

CSales

DSalesData

Attempts:

3 left

💡 Hint

Common Mistakes

Using hyphens in measure names

Starting names with numbers

Using spaces in names

Measure names should not contain hyphens. Using underscore '_' is acceptable and improves readability.

4fill in blank

hard

Fill both blanks to create a properly named calculated table and column.

Power BI

NewTable = SELECTCOLUMNS([1], "[2]", [SalesAmount])

Drag options to blanks, or click blank then click option'

ASales

Bsales

CTotalSales

DTotal-Sales

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase table names

Using hyphens in column names

Using spaces in names

Table names start with uppercase letters without special characters. Column names should be descriptive and use camel case without spaces or special characters.

5fill in blank

hard

Fill all three blanks to define a measure with proper naming conventions and syntax.

Power BI

[1] = CALCULATE(SUM([2][Revenue]), FILTER([2], [2][Region] = "West"))

Drag options to blanks, or click blank then click option'

ATotalRevenue

BSales

CSalesData

Dtotal_revenue

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase measure names

Using inconsistent table names

Using underscores in measure names

Measure names should be descriptive and use camel case starting with uppercase. Table names should be capitalized without special characters. Using the same table name consistently is important.

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