2024: Week 32 - Solution


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



Step 1 - Combine Cards, Pokémon, and Trainer Cards

First we want to input our tables and combine them together to make a single table.

For this we need to make some changes to the tables to ensure that they combine correctly and so we don't have duplicate values. 

First we can look at the Cards input, where we want to split the Leader and the Pokémon fields from the Name field. The name field should become two fields in the format of: [Name]'s [Pokémon] 

Normally, a custom split will use the 's as a separator however in this case using the ' doesn't work so therefore we can write out two separate calculations instead: 

Leader
TRIM(SPLIT([name],"'s",1))

Pokémon 
TRIM(SPLIT([name],"'s",2))

The Pokémon Cards table will now look like this with the additional fields: 


Now we can focus on the 2nd input which is the Pokémon table. For this we need to ensure that we have a single row for each Pokédex # and Name combination. We aren't worried about the other stats so we can just group by these two fields within an Aggregation step: 



Then we can join these tables together using an inner join where Pokémon = Name:



At this stage the table should look like this: 



Then finally we can combine the 3rd table - Training Cards. For this we want to 'stack' these on top of the existing table therefore we using a Union instead of a Join. Some of the fields are missing from the Trainer table so some Null values appear but the table should then look like this: 



Step 2 - Card Type 

Now we want to identify the difference between a Pokémon and a Trainer. For this we can use the Table Names field that is created by the Union step and extract the information from here.

For this we want to split off the value after the last '/' which will provide this information: 



We can then use this field and remove the 'Cards' section by using another split to only return the first word before the ' ' (space) for each row: 



We can then remove any unneeded fields and rename the split field to Card Type. We can also tidy the Leader field by replacing any Null values with 'Leftover Trainers'.

The table should now look like this: 


Step 3 - Card Classifying & Order

Finally we want to classify the cards and order them as per the requirements. For this we want to combine the Leader Order table by using an inner join on Leader:


We can then classify the cards based on the given requirements: 

Card Classifying 
IF [Card]=[Leader]
THEN 1
ELSEIF CONTAINS([Card],'Gym') and [Leader]!='Leftover Trainers'
THEN 2
ELSEIF [Card Type]='Trainer'
THEN 3
ELSE 4
END

Then we can use this classification to sort the cards into the correct order: 



We can then remove any fields that aren't required and our output should look like this: 



You can view the 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

2024: Week 1 - Prep Air's Flow Card

Image
Created by: Carl Allchin Welcome to a New Year of Preppin' Data challenges. For anyone new to the challenges then let us give you an overview how the weekly challenge works.  Each Wednesday the Preppin' crew (Jenny, myself or a guest contributor) drop a data set(s) that requires some reshaping and/or cleaning to get it ready for analysis.  You can use any tool or language you want to do the reshaping (we build the challenges in Tableau Prep but love seeing different tools being learnt / tried). Share your solution on LinkedIn, Twitter/X, GitHub or the Tableau Forums Fill out our tracker so you can monitor your progress and involvement The following Tuesday we will post a written solution in Tableau Prep (thanks Tom) and a video walkthrough too (thanks Jenny) As with each January for the last few years, we'll set a number of challenges aimed at beginners. This is a great way to learn a number of fundamental data preparation skills or a chance to learn a new tool — New Year&
Read more

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

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