ACT NOW: The Alteryx team will be retiring support for Community account recovery and Community email-change requests Early 2026. Make sure to check your account preferences in my.alteryx.com to make sure you have filled out your security questions.
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
My solution:
スポイラ
I chose to select an input file for the dropdown in the first step, as the same method used in step 2 and 3 made the decimals change to underscores in the fieldnames.
That broke the app for those old school tires sizes.
But to keep extra DB files to a minimum, I chose to use a direct input for step 2 and 3, by making the ratio and wheel size values into field names.
That broke the app for those old school tires sizes.
But to keep extra DB files to a minimum, I chose to use a direct input for step 2 and 3, by making the ratio and wheel size values into field names.
A bit annoying the file location seems to be misplaced now.
It is very good exercise that forced to practice iterative app.
Great challenge and exercise on building these types of connected apps.
I used a dynamic rename to get my first list for the drop down, then created NAME|VALUE files for the subsequent apps. I also renamed a few of the fields and shortened the number of decimal places for ratio & rim size to stop the filtering being so tight.
Looking forward to finding new challenges to apply this technique!
