2022: Week 19 - Solution

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


This week we return to our favourite retailer, Chin & Beard Suds Co (C&BSCo) and are looking to identify some mistakes that are coming through within the sales and actual products sold. Let's look at how we solved the problem. 

Step 1 - Combine Size & Sales

First we want to input both the Sales & Size Table sheets from our input. From here we can join these tables by using an inner join on Size = Size ID: 


Then from here we can clean some of the fields by removing Size, Size ID, and renaming Size-1 to Sales Size.

Our table should look like this:



Step 2 - Product Set Correct?

Next we want to include the Product Set table and clean this so that it's in a format that we can join with our previous branch. 

First, we want to ensure that the Product Code field is the same as in the other table. Therefore, we need to remove any of the S codes by using the following calculation: 

Product Code
REPLACE([Product Code],'S','')

Then we want to rename Size to Product Size so that's it's easy to identify when joining later. Our Product Set table should look like this: 


From here we can then start to identify the codes that match and the ones that don't. To do this we can use a couple of joins and change the conditions based on where the Size matches or not. 

First is the Correct Size, here we join where Sales Size = Product Size and Product = Product Code. 


Notice how this excludes some values, and these will be the values where the sizes don't match on both tables. 

Before identifying the wrong sizes, we can remove the Product Code and Sales Size, then we have our first output:



To identify the wrongly matched sizes, we can again use a join, but this time the conditions will be where Product Code = Product and Product Size != Sales Size (does not equal).


Our workflow should now look like this: 



Finally, the last stage is to aggregate the wrongly sized items so we can see the total by Code, Size, and Scent. The aggregate tool has the setup where we group by Product Code, Product Size, and Scent then we can aggregate by summing the total number of rows (renamed to Sales with Wrong Size) for each. 


Our second output should look like this: 



You can download the full output here. 

After you finish the challenge make sure to fill in the participation tracker, then share your solution on Twitter using #PreppinData and tagging @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