- Access exercises (91)
- C# exercises (79)
- Excel exercises (278)
- Power Apps exercises (13)
- Power Automate exercises (18)
- Power BI exercises (139)
- Power Platform exercises ()
- Python exercises (28)
- Report Builder exercises (141)
- SQL exercises (198)
- SSAS exercises (51)
- SSIS exercises (46)
- SSRS exercises (99)
- VBA exercises (85)
- Visual Basic exercises (46)
POWER BI EXERCISES▼
- PowerPivot data models (7)
- Pivot tables using PowerPivot (2)
- Using Excel tables (3)
- Using other data sources (1)
- Transforming data (Power Query) (7)
- Calculated columns (7)
- Measures (2)
- The CALCULATE function (15)
- More advanced DAX functions (5)
- Calendars (1)
- Date functions (10)
- Hierarchies (2)
- KPIs (5)
- Power View (4)
- Power BI Desktop overview (3)
- Power BI Desktop maps (1)
PowerPivot | Power BI Desktop maps exercise | Create a map showing the number of purchases by family
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.
- Go into SQL Server Management Studio;
- Open the SQL file you've just unzipped (you can press CTRL + O to do this); then
- Execute this script.
This will generate the database that you'll need to use in order to do this exercise (note that the database and script are only to be used for exercises published on this website, and may not be reused or distributed in any form without the prior written permission of Wise Owl).
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.
Create a new Power BI Desktop file, and import the following tables:
Import these tables from the Make-a-Mammal database.
Create a map to show the number of purchases by family and postcode:
There are a lot of postcodes, so this looks a bit messy.
From a recent source, import the tblTown table also, and change your map so that the town name is the Location field:
This is not an improvement!
Create a calculated column in the town table to localise things a bit:
Let's pin those towns down to the UK ...
Use this column as your location:
Still a bit messy. Time to filter a bit?
Add a filter to the visualisation to show only South-West data (you can do this by saying that the town's RegionId must equal 7):
Yeah! Finally, a map that looks sensible.
Save this Power BI Desktop file as Cream Teas, then close it down.