In case you missed the announcement: The Alteryx One Fall Release is here! Learn more about the new features and capabilities here
ACT NOW: The Alteryx team will be retiring support for Community account recovery and Community email-change requests after December 31, 2025. Set up your security questions now so you can recover your account anytime, just log out and back in to get started. Learn more 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 #3: Running Averages

KOBoyle
ボリード

Solution attached.  The solution provided seems to assume that the source data will be in chronological order within each HP Category.  I did the sorting within the workflow immediately prior to calculating the averages.

 

Ken

KOBoyle
ボリード

Sean,

I'm not a statistician, but I don't think calculating a moving average with too few data points is correct either.  The "closest value" approach and your approach could both yield significantly skewed results.  Using a stock chart as a familiar use case, the 50-day and 200-day moving average charts do not begin until there are a sufficient number of data points to calculate the average.  With your solution, in Month 2 the 3-month and 6-month averages are the same calculation because only two data points are available. This does not seem right.  Within Alteryx, I think the correct approach is to select 'NULL' for the 'Values for Rows that don't Exist' setting.  This matches the behavior seen in the stock chart example.

 

Ken

A_Twa
アステロイド

This was a real stretch for me - I did finally get to an answer.  However, as others have noted, there seems to be an issue with the provided solution's method for calculating the rolling 6-month avg


This post has been edited by Community Moderation to redact sensitive attachments. The original attachment has been replaced by post_placeholder.txt.

ajmnoble
アトム

This post has been edited by Community Moderation to redact sensitive attachments. The original attachment has been replaced by post_placeholder.txt.

Philip
クエーサー

My solution for Challenge 3.

スポイラ
Weekly Challenge 003.png
sagarb
アステロイド

This is a good challenge. I learnt a new tool and I got to use Transpose and Cross Tab, as I mess up with those 2 tools more than others. I took a bit of help but was able to complete the solution.


This post has been edited by Community Moderation to redact sensitive attachments. The original attachment has been replaced by post_placeholder.txt.

JORGE4900
アステロイド

As some of you already pointed out, the result set does not necessarily match those on the problem. The root cause seems to be that the result set seems to have been compiled without grouping the HP Category on the 6 month multi-row function.

 

Thus, I had difficulty matching the results.


This post has been edited by Community Moderation to redact sensitive attachments. The original attachment has been replaced by post_placeholder.txt.

ADerbak
ボリード

I went through multiple iterations of Multi-Row Tools using IfElse statements with modifying each field for 3mo or 6mo. While this was the right idea, it was lengthy and inefficient. I took a look at what others were doing, and, unfortunately, got so stuck that I referenced the solution file. I have modified for a more efficient process and more like the solution.

 

See attached. 


This post has been edited by Community Moderation to redact sensitive attachments. The original attachment has been replaced by post_placeholder.txt.

MsBindy
アステロイド

I'm always pleased when mine is similar to others.  🙂


This post has been edited by Community Moderation to redact sensitive attachments. The original attachment has been replaced by post_placeholder.txt.

Amarendra
ファイアボール

Attaching the solution for challenge 3. 


This post has been edited by Community Moderation to redact sensitive attachments. The original attachment has been replaced by post_placeholder.txt.