In case you missed the announcement: Alteryx One is here, and so is the Spring Release! Learn more about these new and exciting releases here!
Free Trial

Weekly Challenges

Solve the challenge, share your solution and summit the ranks of our Community!

Also available in | Français | Português | Español | 日本語
IDEAS WANTED

Want to get involved? We're always looking for ideas and content for Weekly Challenges.

SUBMIT YOUR IDEA

Challenge #1: Join to Range

mihaimazareanu
6 - Meteoroid

Here is my solution.

Spoiler
Screenshot Challenge #1.png

SidSaythongphet
8 - Asteroid
Spoiler
 
Challenge 1 Solution.jpg

nikhil_jaju
7 - Meteor

Solution

eolowohunwa
7 - Meteor

My solution

asultanov
8 - Asteroid

Fun!

sidjainudr
5 - Atom

sidjainudr_0-1704750316258.png

I have uploaded result which shows how to use generate rows which will make join very ease.

snbandi
8 - Asteroid

Finished all suggested for Core preparation - and now starting with Starting from Challenges from the beginning.

jdminton
12 - Quasar
Spoiler
Spoiler
 
Snag_3a48a87.png

albracht7
7 - Meteor

Solution attached. 

Spoiler
Grouping Logic: 

IF [Postal Area] >= 2000 AND [Postal Area] <= 2019 then
"R1"
elseif [Postal Area] >= 2020 AND [Postal Area] <= 2039 then "R2"
elseif [Postal Area] >= 2040 AND [Postal Area] <= 2059 then "R3"
elseif [Postal Area] >= 2060 AND [Postal Area] <= 2079 then "R4"
elseif [Postal Area] >= 2080 AND [Postal Area] <= 2100 then "R5"
else
"unknown"
endif

Is there a better way to do this using the other reference table/"Look up table"? It felt like the long way around while I was typing it out. I appreciate any tips!
bmerril6
7 - Meteor
Spoiler
 

(From Range table) -> Text to Columns (separate out ranged years) -> Select (change recently created columns from String to Int)  -> Generate Rows (generate list of postal areas based on the start and end codes of the range) -> Join with Customer table based on Postal Area -> Summarize based on output requested