Bring your best ideas to the AI Use Case Contest! Enter to win 40 hours of expert engineering support and bring your vision to life using the powerful combination of Alteryx + AI. Learn more now, or go straight to the submission form.
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 #273: Filling In The Blanks

Spalders
アステロイド
スポイラ
Spalders_0-1624297537605.png

 

MatthewBr
Alteryx Alumni (Retired)

Nice challenge - Never used Generate Rows before now. 

CandiceDB
Alteryx
Alteryx

My solution:

 

スポイラ
CandiceDB_0-1624306310433.png

 

TonyA
Alteryx Alumni (Retired)

This one is more of a "stream of consciousness" workflow. I didn't plan it out, just started throwing tools on the canvas. Certainly not the recommended way of building out a workflow 🙂. I'm sure it could be tightened up quite a bit.

スポイラ
TonyA_0-1624307349945.png

 

JeffF
Alteryx
Alteryx
スポイラ
JeffF_0-1624311396790.png

 

AkimasaKajitani
17 - Castor
17 - Castor

My solution.

 

スポイラ
AkimasaKajitani_0-1624321672482.png
kelly_gilbert
パルサー

My solution is pretty similar to many others:

 

スポイラ
kelly_gilbert_1-1624327838047.png

 

Since this was a pretty quick one, I decided to experiment with some slightly different configurations, to see if there were performance differences:

スポイラ
I wondered how big of a performance hit I was taking, since I opted for the convenience of the Data Cleansing tool. I tried replacing it with a Formula tool to replace the nulls with zeroes.
kelly_gilbert_1-1624326155294.png

 

Next, I tried moving the Formula tool (to fill in the zeroes for the missing records) to the left output of the join only.
kelly_gilbert_2-1624326279189.png

Results:

スポイラ
I randomly generated a larger test dataset with 2,600 unique client IDs and 636K input records (with the workflow adding 300K records to fill in the blanks), and then ran each configuration 30 times on the same dataset.

Even at that much larger dataset size, the workflow ran in < 5 sec, and Data Cleansing tool added less than 1 sec to the average run time. I was expecting a larger difference. It would be interesting to see how that plays out with an even larger dataset.

Moving the formula tool didn't make a measurable difference in run time, although the measurement isn't very precise.


kelly_gilbert_0-1624326692591.png

 

DaisukeTsuchiya
14 - Magnetar
14 - Magnetar
スポイラ
キャプチャ.JPG

kelvin_law1
コメット

Here is my solution:

スポイラ
kelvinlaw_0-1624329951914.png

 

mike_w
アステロイド

don't take this as an excuse to do any non-essential online shopping! 

スポイラ
mike_w_0-1624332764776.png