We are celebrating the 10-year anniversary of the Alteryx Community! Learn more and join in on the fun here.
Start 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 #33: Reshaping Nielsen Data

CeliaC_Silje
8 - Asteroid

Decided to use Text Input for the column names - if the columns are not dynamic, why not go for a simpler way?

Spoiler
CeliaC_Silje_0-1677567048260.png
Spurs
8 - Asteroid
Spoiler
Spurs_0-1679070498025.png

 

Hammad_Rashid
11 - Bolide

WeeklyChallenge33.JPG

chandler-gjino
Alteryx
Alteryx

Attaching my solution

lucascs
8 - Asteroid
Spoiler
lucascs_0-1684348242830.png

 

lucaskro
8 - Asteroid
Spoiler
lucaskro_0-1685694565439.png

 

ed_hayter
13 - Pulsar
Spoiler
ed_hayter_0-1686584905887.png

 struggled with the input data with this one - really ended up relying on comparing the values to the expected output with my select records which is not very future-proofed. I did like the part of the flow that codes the fields by making a lookup table for a dynamic rename.

 

The_Rad_Valentina
9 - Comet
9 - Comet

Learned that it's important to look at the whole dataset all the way down. 

mithily
8 - Asteroid
Spoiler
spoiler - seemed sort of overly fitted to the data I used the solution but was doing it using record ids myself
ntakeda
12 - Quasar

My solution.

Spoiler
ntakeda_0-1687501487665.png