Challenge #125: US Grand Prix Lap 1 - Data Prep

[JimmyG]

I'm excited to present to you Lap 1 of the 2018 US Grand Prix! If you were at Inspire in Anaheim with us in June, you saw our 3 finalists (@BenMoss, @mattagee, @NicoleJohnson) solve this workflow in front of roughly 3000 Alteryx users and fans. 

Tackling this workflow won't compare to the experience our finalists had, but it will give you a glimpse into what it takes to compete in the Grand Prix. To make it more life-like, I suggest doing the following.

1) Open up the workflow and give yourself 2 minutes to read the prompt - don't touch the mouse!

2) Time yourself - the drivers had a maximum of 12 minutes to finish.*

3) To take it to the next level, invite your friends and neighbors over, provide them food and drinks, and put on some headphones as you solve.

*At Inspire, the journey did begin by the drivers having to find the data in Alteryx Connect - I've provided the data for you in the workflow.

[Kenda]

Off to a running start!

Spoiler

Had never used the Field Summary tool before. Definitely would have felt the pressure in front of 3,00 people!

[LordNeilLord]

Took about 5 mins, so I spent the rest of the checking that all of my values matched....but there are some discrepancies!

I suspect the answer file came from a slightly different source

Spoiler

[AGoyal]

Here is my solution. 

[jasperlch]

Solution attached. Thanks!

[NicoleJohnson]

Well, let me just say that while this round was FAR less stressful than the last one, it was not nearly as fun... :)

Spoiler

Finished this one for the second time in just about 3 minutes - about half the time, and from what I can recall, about half the tools! But then I spent another 3 or so minutes trying to figure out why my answers didn't match when I used the Expect Equal tool... Upon further investigation, I suspect that the solution provided removed the decimal places in the Pay Rate field (turning $14.00 into  $1400, etc.), which is resulting in the difference in min/max data for the Pay Rate field. Otherwise, looks like a match (and based on the requirements of the Join, was technically a match for the requirements of the challenge despite the difference in the Pay Rate field).

Nice to get a chance to relive this one in a less intense environment haha! But I would still go back and take that on-stage adrenaline rush any day... :)

Cheers! (Now, to go study up again on what on earth went wrong in Round Two, just in case that one is next in the pipeline...)

NJ

[Ladarthure]

Great Challenge!

[KevinW]

 I love my formulas (and to be honest, I forgot about the datetime tool)!  ah well, it saved me one tool in the workflow.

Spoiler

[patrick_digan]

Spoiler

1) Perhaps I'm missing something, but don't we need to address the duplicate employee id's before we join? It seems like 1204033041 is listed twice in both files. I sorted the data and then used a multi-row formula tool to add a grouped by record ID.
2) I don't think we have the exact same starting dataset as some of the values in the answer don't match the values coming from my solution.

[svenk]

My Solution!