2020: Week 26

This week's challenge is inspired by some real life consulting work, replacing a very manual task with an automated process! Unique IDs are a great way to label your data, but issues can arise when trying to match internal IDs to 3rd Party IDs, as there could have been changes made to the naming convention by any number of people.

So how do we go about making some educated guesses and getting together a list of IDs that we can take back to the 3rd Party to complain about?

Input

1 input this week, with 2 sheets:



Requirements

  • Input the data.
  • Find the IDs that match perfectly and label them as such.
  • For the remaining unmatched Internal and 3rd Party IDs, create all the possible matching IDs for each Scent.
  • For each 3rd Party ID, find the Internal ID with the lowest sales difference. 
  • For each Internal ID, find the 3rd Party ID with the lowest sales difference.
    • You should now have no duplicated IDs.
  • Classify these IDs as "Matched on Scent".
  • Join these IDs to the "Matched IDs".
  • Classify IDs from Internal and 3rd Party Data which have not been matched and join these to create the output.
  • Output the data. 

Output



  • 6 fields
    • Status
    • ID
    • 3rd Party ID
    • Scent
    • Sales
    • 3rd Party Sales
  • 49 rows (50 including headers)


The full output can be found here for comparison.

Make sure to fill in the participation tracker, share using #PreppinData on Twitter and post you solutions onto our Tableau Forums community page so that we can compare our workflows! 

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