The link to last week’s challenge (challenge #21) is HERE.
This week’s challenge is a little special. I have mentioned before that as internal users or Alteryx we all do these exercises every week and we started doing this at the beginning of 2014. There have been a lot of exercises since then and the product has changed a lot of the past few years. The exercise posted here is exercise #1, the inaugural exercise that we completed internally.
In the spirit of that, you will find the workflow will build from top down instead of from left to right, that is the way Alteryx used to work. For some more fun I would ask that before building the workflow, go to the “About” box from the HELP menu and double click the Colorado flag next to the text “Created in Boulder, Colorado” after that, the tool icons will change to the original Alteryx tool icons that used to be in the product. Don’t worry, once you close Alteryx and re-open it the icons will return to normal.
Now for the challenge , this week’s challenge is an intermediate difficulty one that requires parsing a text field to get at values to summarize.
Use case: The log files from an ATM machine have the transaction amounts embedded in text strings. The user needs to have these text amounts summarized by row (transaction).
Objective: For this assignment the numbers directly following the text ‘ATM2.’ are dollar amounts for transactions. Summarize the values on a row by row basis.
Hello @alexey_nikityuk and welcome to our community!
These exercises are for users of all abilities to sharpen their skills and develop new ones. We love feedback and we want to know your experience with the exercise. Every Monday, @GeneR posts a new exercise and a solution for the previous week. I will comment with a screenshot of Gene's solution in the Spoiler text like this
Feel free to play along! There are so many ways to solve a problem in Alteryx. We'd love to see how you arrive at the answer!
Love that easter egg to move this into the old icon format @GeneR
took a similar but slightly different approach than @MarqueeCrew