2024: Week 44 - Solution



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


Step 1 - Sold & Returned

First we want to tidy the dates a item was sold or returned so that the return date isn't before a sale date.

We can identify any issues by creating an issue flag: 

Issue?
[Date Sold]>=[Date Returned]

Then using this to recalculate the Order or Return date: 

Order Date
IF [Issue?]
THEN [Date Returned]
ELSE [Date Sold]
END


Return Date 
IF [Issue?]
THEN [Date Sold]
ELSE [Date Returned]
END

We can then remove the Issue?, Date Sold, & Date Returned fields.

Finally, we can calculate how many days it took to return an item by using a DateDiff function: 

Days to Return 
DATEDIFF('day',[Order Date],[Return Date])

And also calculate what the value of the returned items are: 

Return Value 
IF [Days to Return]<=60
THEN [Price ]
ELSEIF [Days to Return]<=100
THEN round([Price ]*0.5,2)
ELSEIF [Days to Return]>100
THEN 0
END

At this stage our table looks like this: 



Step 2 - Calculate Output Metrics

There are various different metrics that are required for the output, but we need to do some cleaning beforehand in order to calculate these.

First we can focus on the returned items and their value. Once we've created a new clean step we can use a filter to retain only the returned item (Exclude Nulls from the Return Date field). Then we can calculate the totals using an aggregate step.

Within the aggregate we want to group by Return Date, then Sum the Return Value and Number of Rows field, and also find the Avg of the Days to Return field: 


We can then tidy up the fields by renaming Return Value to Total Returns Value, Number of Rows to Number of Returns, and rounding the Avg Days to Return to 2 decimal places (ROUND([Days to Return],2))

We can then calculate the revenue using a new branch before we filtered for the Returned values. This time we want an aggregate step where we group by Order Date and Sum the Price: 



We can then round this value and rename the field to Revenue: 

Revenue 
ROUND([Price ],2)


Finally we can combine the Returns and Revenue branches by using a join where Return Date = Order Date and we return all of the rows from the orders Revenue branch: 


After renaming and removing any additional fields we are ready to output our data: 



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