SSAS - tabular | Measures exercise | Using CALCULATE to split purchases into cheap and expensive

This exercise is provided to allow potential course delegates to choose the correct Wise Owl Microsoft training course, and may not be reproduced in whole or in part in any format without the prior written consent of Wise Owl.

The answer to the exercise will be included and explained if you attend the course listed below!

Software ==> SSAS - tabular  (29 exercises)
Version ==> SSAS 2012 and later
Topic ==> Measures  (3 exercises)
Level ==> Relatively easy
Course ==> SSAS - Tabular Model
Before you can do this exercise, you'll need to download and unzip this file (if you have any problems doing this, click here for help).

You need a minimum screen resolution of about 700 pixels width to see our exercises. This is because they contain diagrams and tables which would not be viewable easily on a mobile phone or small laptop. Please use a larger tablet, notebook or desktop computer, or change your screen resolution settings.

If you haven't already done so, run the SQL script in the above folder in SQL Server Management Studio to generate a database (not for commercial use or copying) called MAM

Again if you haven't already done so, create a new project called BaseModel, and import the following tables: tblAnimal, tblCentre, tblCentreType, tblPos, tblProduct, tblRegion, tblSpecies, tblStore, tblTown, tblTransaction

Delete any existing measures from your model, and create one to show the sum of the quantity of goods sold, to show in a pivot table:

The total sales by species

Don't cheat and use the AutoSum tool, but instead type in your measure!


Now use the CALCULATE function to create two measures as follows:

Name What it does
Cheap Shows the sum of quantity sold where the price of the transaction is £10 or less.
Expensive Shows the sum of the quantity sold where the transaction price is more than £10.

Use these to show the following pivot table:

Cheap and expensive goods

The figures shown here are by species, but they will remain correct whatever combination of slicers, row and column fields you choose to display.


If required, use DAX Editor to save your measures in a .dax file called Easier than I thought, and save your Excel workbook with the same name.

This page has 0 threads Add post