Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

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

seven
12 - Quasar

Hi Nikos,

 

in this case, the Generate Rows tool would limit the amount of data. However, I don't typically use the tool as a first pass.

 

Each region's range has 20 Postal Areas. Generating Rows for each region multiplies the data by 20. I multiplied by 5. While there are only 5 regions getting 20x and I'm multiplying a larger data set by 5x, my solution scales much better in real world applications.

 

Imagine a case in which you have a date, cost, and item. The dataset is 30MM+ records. You want to sum the costs per item over a rolling period of 12 months. If you create a date 12 months back for each row and use the Generate Rows tool to duplicate each row by 365 and self join, the join will be monstrous, use all the memory of your machine, and crash 10 hours later. You are multiplying 30MM+ records by 365 to almost 11 billion records and then self join. Or, you can create a cartesian product using the Join on item only and then filter the records out that don't fit the rolling 12 month period. Now, you can finally sum.

 

I experimented using both solutions and put the second one into production some time ago. While the Generate Rows would work in this artificially small and contrived dataset, it wouldn't scale well. Finally, It wouldn't be much fun if I posted the same old solution as everyone else.

justindavis
10 - Fireball
Spoiler
Generate Rows for the win. 5 Minutes - and to think I had to skip this one when I first started these in the spring!

challenge_1_solution_justindavis.PNG
FRANCK_ROUQUETTE
8 - Asteroid
Good exercises - thanks
spenderr
5 - Atom
Spoiler
Challenge 1 Screenshot.PNG

Think this is a bit easier now 

bartleb
6 - Meteoroid

Learned some new functions available and now that I know more about how Generate rows works I'd consolidate a little bit, but it works.

sbuday3
6 - Meteoroid

Attached is my solution.

ken_yap_au
8 - Asteroid

I chose to generate rows directly from the Input without a formula, although I think splitting out your ranges would make the workflow easier to follow. 

Adam_Dooley
8 - Asteroid

Tile tool baby!

ZacPhan
6 - Meteoroid

Hi there,

 

As attached is a screenshot of my workflow and the file!

Spoiler
clipboard_image_0.png
Billigans
8 - Asteroid
Spoiler


A little late to the party here, but ...

I went about it a little differently than most submissions I saw. I used the formula bar to generate the Region code based on the value in the data. Let me know if anyone has any critiques. challenge_1_solution_BL.png