Exercise 1:

Create DAX Calculations in Power BI Desktop,

Part 1
Create
Calculated
Tables

The estimated time to complete the lab is 45 minutes.

Exercise 2:
Create Measures
In this lab you will create calculated tables, calculated columns, and simple measures using Data Analysis
Expressions (DAX).

In this lab you learn how to:

Create calculated tables

Create calculated columns

Create measures

Lab story

This lab is one of many in a series of labs that was designed as a complete story from data preparation to
publication as reports and dashboards. You can complete the labs in any order. However, if you intend to work
through multiple labs, we suggest you do them in the following order:

1. Prepare Data in Power BI Desktop

2. Load Data in Power BI Desktop

3. Design a Data Model in Power BI

4. Create DAX Calculations in Power BI Desktop, Part 1

5. Create DAX Calculations in Power BI Desktop, Part 2

6. Design a Report in Power BI Desktop, Part 1

7. Design a Report in Power BI Desktop, Part 2

8. Analyze Data with AI Visuals

9. Create a Power BI Dashboard

10. Enforce Row-Level Security

Exercise 1: Create Calculated Tables

In this exercise you will create two calculated tables. The first will be the Salesperson table, to allow a direct
relationship between it and the Sales table. The second will be the Date table.

Task 1: Get started

In this task you will setup the environment for the lab.

Important: If you are continuing on from the previous lab (and you completed that lab successfully), do not
complete this task; instead, continue from the next task.

1. To open the Power BI Desktop, on the taskbar, click the Microsoft Power BI Desktop shortcut.

1. To close the getting started window, at the top-left of the window, click X.
 1. To open the starter Power BI Desktop file, click the File ribbon tab to open the backstage view.

2. Select Open Report.

1. Click Browse Reports.

1. In the Open window, navigate to the D:\PL300\Labs\04-create-dax-calculations-in-power-bi-

desktop\Starter folder.

2. Select the Sales Analysis file.

3. Click Open.

1. Close any informational windows that may open.

2. To create a copy of the file, click the File ribbon tab to open the backstage view.

3. Select Save As.

1. If prompted to apply changes, click Apply.

1. In the Save As window, navigate to the D:\PL300\MySolution folder.

2. Click Save.

Task 2: Create the Salesperson table

In this task you will create the Salesperson table (direct relationship to Sales).
1. In Power BI Desktop, in Report view, on the Modeling ribbon, from inside the Calculations group, click
New Table.

2. In the formula bar (which opens directly beneath the ribbon when creating or editing calculations), type
Salesperson =, press Shift+Enter, type ‘Salesperson (Performance)’, and then press Enter.

For your convenience, all DAX definitions in this lab can be copied from the snippets file, located in
D:\PL300\Labs\04-create-dax-calculations-in-power-bi-desktop\Assets\Snippets.txt.

A calculated table is created by first entering the table name, followed by the equals symbol (=), followed by a
DAX formula that returns a table. Note that the table name cannot already exist in the data model.

The formula bar supports entering a valid DAX formula. It includes features like auto-complete, Intellisense
and color-coding, enabling you to quickly and accurately enter the formula.

This table definition creates a copy of the Salesperson (Performance) table. It copies the data only, however
model properties like visibility, formatting, etc. are not copied.

Tip: You’re encouraged to enter “white space” (i.e. carriage returns and tabs) to layout formulas in an intuitive
and easy-to-read format—especially when formulas are long and complex. To enter a carriage return, press
Shift+Enter. “White space” is optional.

3. In the Fields pane, notice that the table icon is a shade of blue (denoting a calculated table).

Calculated tables are defined by using a DAX formula which returns a table. It’s important to understand that
calculated tables increase the size of the data model because they materialize and store values. They’re
recomputed whenever formula dependencies are refreshed, as will be the case for this data model when new
(future) date values are loaded into tables.

Unlike Power Query-sourced tables, calculated tables can’t be used to load data from external data sources.
They can only transform data based on what has already been loaded into the data model.

4. Switch to Model view.

5. Notice that the Salesperson table is available (take care, it might be hidden from view, in which case scroll
horizontally to locate it).

6. Create a relationship from the Salesperson | EmployeeKey column to the Sales | EmployeeKey column.
 7. Right-click the inactive relationship between the Salesperson (Performance) and Sales tables, and then
select Delete.

8. When prompted to confirm the deletion, click OK.

9. In the Salesperson table, multi-select the following columns, and then hide them (set the Is Hidden
property to Yes):

EmployeeID

EmployeeKey

UPN

10. In the model diagram, select the Salesperson table.

11. In the Properties pane, in the Description box, enter: Salesperson related to Sales

You may recall that descriptions appear as tooltips in the Fields pane when the user hovers their cursor over a
table or field.

12. For the Salesperson (Performance) table, set the description to: Salesperson related to region(s)

The data model now provides two alternatives when analyzing salespeople. The Salesperson table allows
analyzing sales made by a salesperson, while the Salesperson (Performance) table allows analyzing sales
made in the sales region(s) assigned to the salesperson.

Task 3: Create the Date table

In this task you will create the Date table.

1. Switch to Data view.

2. On the Home ribbon tab, from inside the Calculations group, click New Table.

3. In the formula bar, enter the following:

DAX

Code  Copy

Date =
CALENDARAUTO(6)
 The CALENDARAUTO() function returns a single-column table consisting of date values. The “auto” behavior
scans all data model date columns to determine the earliest and latest date values stored in the data model. It
then creates one row for each date within this range, extending the range in either direction to ensure full
years of data is stored.

This function can take a single optional argument that is the last month number of a year. When omitted, the
value is 12, meaning that December is the last month of the year. In this case, 6 is entered, meaning that June
is the last month of the year.

4. Notice the column of date values.

The dates shown are formatted using US regional settings (i.e. mm/dd/yyyy).

5. At the bottom-left corner, in the status bar, notice the table statistics, confirming that 1826 rows of data
have been generated, which represents five full years’ data.

Task 4: Create calculated columns

In this task you will add additional columns to enable filtering and grouping by different time periods. You will
also create a calculated column to control the sort order of other columns.

For your convenience, all DAX definitions in this lab can be copied from the snippets file, located in
D:\PL300\Labs\04-create-dax-calculations-in-power-bi-desktop\Assets\Snippets.txt.

1. On the Table Tools contextual ribbon, from inside the Calculations group, click New Column.

2. In the formula bar, type the following (or copy from the snippets file), and then press Enter:

DAX

Code  Copy

Year =
"FY" & YEAR('Date'[Date]) + IF(MONTH('Date'[Date]) > 6, 1)

A calculated column is created by first entering the column name, followed by the equals symbol (=), followed
by a DAX formula that returns a single-value result. The column name cannot already exist in the table.

The formula uses the date’s year value but adds one to the year value when the month is after June. It’s how
fiscal years at Adventure Works are calculated.

3. Verify that the new column was added.

4. Use the snippets file definitions to create the following two calculated columns for the Date table:

Quarter

Month

5. To validate the calculations, switch to Report view.

6. To create a new report page, at the bottom-left, click the plus icon.

7. To add a matrix visual to the new report page, in the Visualizations pane, select the matrix visual type.

Tip: You can hover the cursor over each icon to reveal a tooltip describing the visual type.

8. In the Fields pane, from inside the Date table, drag the Year field into the Rows well/area.

9. Drag the Month field into the Rows well/area, directly beneath the Year field.
10. At the top-right of the matrix visual (or bottom, depending on the location of the visual), click the forked-
double arrow icon (which will expand all years down one level).

11. Notice that the years expand to months, and that the months are sorted alphabetically rather than
chronologically.

By default, text values sort alphabetically, numbers sort from smallest to largest, and dates sort from earliest
to latest.

12. To customize the Month field sort order, switch to Data view.

13. Add the MonthKey column to the Date table.

DAX

Code  Copy

MonthKey =
(YEAR('Date'[Date]) * 100) + MONTH('Date'[Date])

This formula computes a numeric value for each year/month combination.

14. In Data view, verify that the new column contains numeric values (e.g. 201707 for July 2017, etc.).

15. Switch back to Report view.

16. In the Fields pane, ensure that the Month field is selected (when selected, it will have a dark gray
background).
 17. On the Column Tools contextual ribbon, from inside the Sort group, click Sort by Column, and then
select MonthKey.

18. In the matrix visual, notice that the months are now chronologically sorted.

Task 5: Complete the Date table

In this task you will complete the design of the Date table by hiding a column and creating a hierarchy. You will
then create relationships to the Sales and Targets tables.

1. Switch to Model view.

2. In the Date table, hide the MonthKey column (set Is Hidden to Yes).

3. On the Fields right side pane, select the Date table, right click on the Year column, and select create
hierarchy.
4. Rename newly created hierarchy to Fiscal by right click and Rename.

5. Add the follow two remaining fields to the Fiscal hierachy by selecting them in the fields pane, right
clicking, selecting Add to hierarchy -> Fiscal.

Quarter

Month
 6. Create the following two model relationships:

Date | Date to Sales | OrderDate

Date | Date to Targets | TargetMonth

7. Hide the following two columns:

Sales | OrderDate

Targets | TargetMonth

Task 6: Mark the Date table

In this task you will mark the Date table as a date table.

1. Switch to Report view.

2. In the Fields pane, select the Date table (not the Date field).

3. On the Table Tools contextual ribbon, from inside the Calendars group, click Mark as Date Table, and
then select Mark as Date Table.

4. In the Mark as Date Table window, in the Date Column dropdown list, select Date.

5. Click OK.
 6. Save the Power BI Desktop file.

Power BI Desktop now understands that this table defines date (time). It’s important when relying on time
intelligence calculations. You’ll work with time intelligence calculations in the Create DAX Calculations in
Power BI Desktop, Part 2 lab.

Note that this design approach for a date table is suitable when you don’t have a date table in your data
source. If you have a data warehouse, it would be appropriate to load date data from its date dimension table
rather than “redefining” date logic in your data model.

Exercise 2: Create Measures

In this exercise you will create and format several measures.

Task 1: Create simple measures

In this task you will create simple measures. Simple measures aggregate values in a single column or count rows
of a table.

1. In Report view, on Page 2, in the Fields pane, drag the Sales | Unit Price field into the matrix visual.

The labs use a shorthand notation to reference a field. It will look like this: Sales | Unit Price. In this example,
Sales is the table name and Unit Price is the field name.

You may recall that in the Model Data in Power BI Desktop lab, you set the Unit Price column to
summarize by Average. The result you see in the matrix visual is the monthly average unit price (sum of unit
price values divided by the count of unit prices).

2. In the visual fields pane (located beneath the Visualizations pane), in the Values field well/area, notice that
Unit Price is listed.

3. Click the down-arrow for Unit Price, and then notice the available menu options.
 Visible numeric columns allow report authors at report design time to decide how column values will
summarize (or not). It can result in inappropriate reporting. Some data modelers don’t like leaving things to
chance, however, and choose to hide these columns and instead expose aggregation logic defined in
measures. It’s the approach you will now take in this lab.

4. To create a measure, in the Fields pane, right-click the Sales table, and then select New Measure.

5. In the formula bar, add the following measure definition:

DAX

Code  Copy

Avg Price =
A
‎VERAGE(Sales[Unit Price])

6. Add the Avg Price measure to the matrix visual.

7. Notice that it produces the same result as the Unit Price column (but with different formatting).

8. In the Values well, open the context menu for the Avg Price field, and notice that it is not possible to
change the aggregation technique.
 It’s not possible to modify the aggregation behavior of a measure.

9. Use the snippets file definitions to create the following five measures for the Sales table:

Median Price

Min Price

Max Price

Orders

Order Lines

The DISTINCTCOUNT() function used in the Orders measure will count orders only once (ignoring duplicates).
The COUNTROWS() function used in the Order Lines measure operates over a table.

In this case, the number of orders is calculated by counting the distinct SalesOrderNumber column values,
while the number of order lines is simply the number of table rows (each row is a line of an order).

10. Switch to Model view, and then multi-select the four price measures: Avg Price, Max Price, Median Price,
and Min Price.

11. For the multi-selection of measures, configure the following requirements:

Set the format to two decimal places

Assign to a display folder named Pricing

12. Hide the Unit Price column.

 The Unit Price column is now not available to report authors. They must use the pricing measures you’ve
added to the model. This design approach ensures that report authors won’t inappropriately aggregate prices,
for example, by summing them.

13. Multi-select the Order Lines and Orders measures, and then configure the following requirements:

Set the format use the thousands separator

Assign to a display folder named Counts

14. In Report view, in the Values well/area of the matrix visual, for the Unit Price field, click X to remove it.

15. Increase the size of the matrix visual to fill the page width and height.

16. Add the following five measures to the matrix visual:

Median Price

Min Price

Max Price

Orders

Order Lines

17. Verify that the results looks sensible and are correctly formatted.

Task 2: Create additional measures

In this task you will create additional measures that use more complex formulas.

1. In Report view, select Page 1.

2. Review the table visual, noticing the total for the Target column.
3. Select the table visual, and then in the Visualizations pane, remove the Target field.

4. Rename the Targets | Target column as Targets | TargetAmount.

Tip: There are several ways to rename the column in Report view: In the Fields pane, you can right-click the
column, and then select Rename—or, double-click the column, or press F2.

You’re about to create a measure named Target. It’s not possible to have a column and measure in the same
table with the same name.

5. Create the following measure on the Targets table:

DAX

Code  Copy

Target =

IF(

HASONEVALUE('Salesperson (Performance)'[Salesperson]),

SUM(Targets[TargetAmount])

The HASONEVALUE() function tests whether a single value in the Salesperson column is filtered. When true,
the expression returns the sum of target amounts (for just that salesperson). When false, BLANK is returned.

6. Format the Target measure for zero decimal places.

Tip: You can use the Measure Tools contextual ribbon.

7. Hide the TargetAmount column.

Tip: You can right-click the column in the Fields pane, and then select Hide.

8. Add the Target measure to the table visual.

9. Notice that the Target column total is now BLANK.

10. Use the snippets file definitions to create the following two measures for the Targets table:

Variance

Variance Margin

11. Format the Variance measure for zero decimal places.

12. Format the Variance Margin measure as percentage with two decimal places.

13. Add the Variance and Variance Margin measures to the table visual.

14. Resize the table visual so all columns and rows can be seen.

While it appears all salespeople are not meeting target, remember that the table visual isn’t yet filtered by a
specific time period. You’ll produce sales performance reports that filter by a user-selected time period in the
Design a Report in Power BI Desktop, Part 1 lab.

15. At the top-right corner of the Fields pane, collapse and then expand open the pane.

Collapsing and re-opening the pane resets the content.

16. Notice that the Targets table now appears at the top of the list.
 Tables that comprise only visible measures are automatically listed at the top of the list.

Task 3: Finish up

In this task you will complete the lab.

1. Save the Power BI Desktop file.

2. If you intend to start the next lab, leave Power BI Desktop open.

You’ll enhance the data model with more advanced calculations using DAX in the Create DAX Calculations
in Power BI Desktop, Part 2 lab.