community
cancel
Showing results for 
Search instead for 
Did you mean: 
Do you have the skills to make it to the top? Subscribe to our weekly challenges. Try your best to solve the problem, share your solution, and see how others tackled the same problem. We share our answer too.
Weekly Challenge
Do you have the skills to make it to the top? Subscribe to our weekly challenges. Try your best to solve the problem, share your solution, and see how others tackled the same problem. We share our answer too.
Unable to display your progress at this time. Please try again a little later, or contact an administrator if you continue to see this error.
Getting started with Designer? | Start your journey with our new Learning Path!

Challenge #167: Grand Prix 2019

Alteryx
Alteryx

Here's my solution. I think it could do with some trimming, but it works.

Asteroid

I didn't use the Driver Standings input data at all, but still came to the same result.  It took an hour compared to the 10 minutes or so for the LIVE Grand Prix. 

Spoiler
Challege 167 Spoiler.png 

 

Asteroid

Nice job @TonyA.  I didn't have to use the Driver Standings input either.

 

Well done @john_miller9. Nice use of the Download tool to query Wikipedia for extra credit.

 

Agreed @bnelly1987.  Useless Driver Standings data.

Alteryx Certified Partner

Here's my solution

 

Spoiler
Screenshot 2019-06-24 at 20.09.20.png
Meteoroid
Spoiler
Spoiler Alert #167.JPG
Alteryx
Alteryx
 
Alteryx Partner

Here's mine!

I did not use one of the input tables...

 

Spoiler
キャプチャ.PNG
Meteor
Spoiler
challene167.PNG
Meteoroid

Question for you.  I have only been using Alteryx for a few weeks....just passed the Core exam last night.  When you build workflows like this, what is your technique for knowing which fields to de-select in your joins?  Do you de-select as you go, or once you get to the next step and verify what you need, do you go back and de-select fields in the previous step to streamline?

Tried a very simple approach without any complicated operations/functions.

Suggestions and criticism always welcome!

 

Capture.PNG