2023: Week 10 - Solution

 

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


Building on our challenge from last week, we want to take this a step further and allow users to find out their balance, even on days that they don't make a transaction. 

Step 1 - Balance Each Day

First, we need to calculate the order in which the transactions were made and the total value for each of the days.

To calculate the total transaction value we can use a LOD where we group by Account Number and Balance Date and then Sum the Transaction Value. 


From here we can then order the transactions using a Rank calculation where we group by Account Number and then Rank the Balance Date Ascending and Transaction Value Descending. 


From here, we then only want to take the single transaction from each day so we can identify the latest transaction (max Order) from each account number and balance date combination.


Using this max order, we can filter where Max Order = Order, so that we only have a single, latest transaction for each day. 

After tidying some fields, we want to rename the Total Transaction Value to Transaction Value and the table should look like this: 


Step 2 - Next Transaction

Next we need to identify the 'gap' in days between transactions so that we can scaffold the missing days. 

For this we want to calculate the transaction order for each Account Number using a Rank calculation: 


We then want to bring the next transaction date onto the same row as the current transaction so that we can use the dates to scaffold the data later in the workflow.

To do this want want to use a self-join, so need to create a separate clean step where we remove the Transaction Value and Balance fields. We can then -1 from the Transaction Order field, so that it aligns with the order of the previous transaction. 

Finally, we want to -1 from each of the days to create an upper bound for each of the dates. We do this as we don't want to include the next transaction date within the scaffold because there's already data for this within the table.

Balance Date Upper Bound 
DATE(DATEADD('day',-1,[Balance Date]))

After the calculation, we can remove the Balance Date and the new clean step table should look like this: 


We can now create the self-join to align the current and previous orders using a Left-Inner Join on Account Number and Transaction Order.


Our new table now looks like this:


The last action we need to take at this stage is to ensure that are no null dates within the Balance Date Upper Bound field. If there are nulls we want to replace them with the latest date in the upper bound field. 

Therefore we first need to identify the latest date using a LOD: 


Then use an IF statement to replace the nulls: 

Balance Date Upper Bound 
IF ISNULL([Balance Date Upper Bound])
THEN [Max Balance Date]
ELSE [Balance Date Upper Bound]
END

Our table should now look something like this: 


Step 3 - Scaffold Table

Now we have prepared the table we are now ready to scaffold the missing dates. We can utilise the New Rows step within Tableau Prep to do this easily. 

Within the New Rows step we want to add rows in the range where Balance Date <= Balance Date Upper Bound where we're adding a single day. We also need to make sure that the balance is carried over from the previous row. 

As a result we should start to generate some rows that look like this: 


Then finally we need to ensure that the transaction value is null on the days that no transaction was made. 

Transaction Value 
IF [Balance Date]=[Date] THEN [Transaction Value]
ELSE NULL
END

When we remove the unneeded fields our table should now look like this: 


Step 4 - Date Selection Parameter

The final task for this week is to create a date parameter so that the user can select a date to show the balances on this day.

First, we need to duplicate the Date field and then convert it to a string. We can then create a parameter that is a string with a list of dates that you want the user to select. Unfortunately, there is no option to auto-fill these dates based on a field like you can in Tableau Desktop and no Date option so that's why we're using a string!


From here we can use this parameter within a filter where [Parameters.Select a date]=[Date-1]

Then remove both date fields and add the parameter into the Output so that the table name is 'Balance as of <Select a Date>'. This will change the name of the output based on the parameter selected by the user: 


Our final table should look like this where 2023-02-01 is selected: 


You can download all 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 @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