2023: Week 20 - Solution



Solution by Tom Prowse and you can download the workflow here. 


This week's challenge comes from Trea McElhone and we are looking at food options at our school dining hall.

Step 1 - Group Meal Types

First we want to input our Meal Nutritional Info table where we can group the meal types into different types of food (Meat-based, Vegan, Vegetarian). 

To do this we can make use of Tableau Prep's grouping features by using the set group by pronunciation or manually group the fields as there aren't too many to group. 

If we are manually grouping then all we need to do is select the given fields in the profile pane and then right-click --> group values 



Step 2 - Combine Tables

We can now input the 2nd table that contains details about the Meal Prices. We can join the table with our existing workflow by using an inner join on the Meal Option field. 



After removing the irrelevant fields our table should look like this: 



Step 3 - % of Total

Final part of the challenge is to calculate the avg. price per type of meal and what % of the total each type makes up. 

First we want to calculate the total per type and the average price. To do this we can use an aggregation step to group by Type, Avg. Price, Count Meal Option


From here we can use these fields to calculate the % of total for each type. First we need to calculate the total number of meals across all types. We can do this by using a Fixed LOD calculation: 

Total Count 


We can then use this to calculate the percentage which is rounded to the nearest whole number: 

Percent of Total 
ROUND(([Meal Option]/[Total Count])*100,0)

We can then remove and rename some fields so that our table is then ready to output: 



After you finish the challenge make sure to fill in the participation tracker, then share your solution on Twitter using #PreppinData and tagging Trea McElhone, @Datajedininja, @JennyMartinDS14 & @TomProwse1

You can also post your solution on the Tableau Forum where we have a Preppin' Data community page. Post your solutions and ask questions if you need any help! 


Popular posts from this blog

2023: Week 1 The Data Source Bank

Image
 Created by: Carl Allchin Welcome to a New Year of Preppin' Data. These are weekly exercises to help you learn and develop data preparation skills. We publish the challenges on a Wednesday and share a solution the following Tuesday. You can take the challenges whenever you want and we love to see your solutions. With data preparation, there is never just one way to complete the tasks so sharing your solutions will help others learn too. Share on Twitter, LinkedIn, the Tableau Forums or wherever you want to too. Tag Jenny Martin, Tom Prowse or myself or just use the #PreppinData to share your solutions.  The challenges are designed for learning Tableau Prep but we have a broad community who complete the challenges in R, Python, SQL, DBT, EasyMorph and many other tools. We love seeing people learn new tools so feel free to use whatever tools you want to complete the challenges.  A New Year means we start afresh so January's challenges will be focused on beginners. We will use dif
Read more

2023: Week 2 - International Bank Account Numbers

Image
Challenge By: Jenny Martin For week 2 of our beginner month, Data Source Bank has a requirement to construct International Bank Account Numbers (IBANs), even for Transactions taking place in the UK. We have all the information in separate fields, we just need to put it altogether in the following order: Inputs A list of the transactions, with information about the receiving bank account  A lookup table for the SWIFT Bank Codes  Requirements Input the data In the Transactions table, there is a Sort Code field which contains dashes. We need to remove these so just have a 6 digit string ( hint ) Use the SWIFT Bank Code lookup table to bring in additional information about the SWIFT code and Check Digits of the receiving bank account ( hint ) Add a field for the Country Code ( hint ) Hint: all these transactions take place in the UK so the Country Code should be GB Create the IBAN as above ( hint ) Hint: watch out for trying to combine sting fields with numeric fields - check data types Re
Read more

How to...Handle Free Text

Image
Free isn't always a good thing. In data, Free text is the example to state when proving that statements correct. However, lots of benefit can be gained from understanding data that has been entered in Free Text fields. What do we mean by Free Text? Free Text is the string based data that comes from allowing people to type answers in to systems and forms. The resulting data is normally stored within one column, with one answer per cell. As Free Text means the answer could be anything, this is what you get - absolutely anything. From expletives to slang, the words you will find in the data may be a challenge to interpret but the text is the closest way to collect the voice of your customer / employee. The Free Text field is likely to contain long, rambling sentences that can simply be analysed. If you count these fields, you are likely to have one of each entry each. Therefore, simply counting the entries will not provide anything meaningful to your analysis. The value is in
Read more