2023: Week 31 - Solution



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



This is our first week where we revisit another HR focused month with some challenges provided by Kelly Gilbert. 

For the first challenge we look at filling in missing IDs from various different tables. 

Step 1 - Lookup Table

First we want to create a lookup table to identify the unique IDs from each table. We can input both tables and create an aggregate step after each step. Within these aggregations we want to make a unique list of the employee id's and the guid's so we can group by both of these fields: 


We can then use a union step to bring both branches together and create a long table with all the IDs: 


From there we can remove the Table Names field and then filter the table to remove any fields that are Null in both the employee id and guid fields. We can filter using this calculation: 

NOT ISNULL([employee_id])
AND 
NOT ISNULL([guid])

Then finally we can use another aggregation field to remove any duplicate values by grouping by employee_id and guid: 


At this stage our table should look like this: 



Step 2 - Dimension Table

We now want to utilise the newly created lookup table to fill in any missing ids from the original table. 

First we want to use an outer join between the dim table and the lookup table, where we include all of the rows from the dim table, and join on the guid. 



This provides us with the lookup table and dim table, so we can merge both of the ID fields and both of the employee id fields to remove some null values.

However, there are still some remaining null values in the guid field, therefore we can utilise the lookup table again by joining it using the same outer join but this time joining on employee_id: 


Again, we can merge both of the employee_id and guid fields so that we have a complete table with no missing ID fields.

Our first output should look like this:



Step 3 - Monthly Table

The final stage of the challenge involves us following the same process again, but this time for the monthly table. We want to repeat the following steps, but on a separate branch and on the monthly table: 

1. Outer join with the lookup table using the guid field then merge both of the id fields:


2. Outer join with the lookup table using the employee_id field and then merge both of the id fields: 


After this the output should look like this: 



You can download the output from here.

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