Cloud Quests

mikecusic · ‎04-02-2025

Hi Community,

We posted the solution JSON file to Cloud Quest #30. Check it out and let us know what you think! Send suggestions to academy@alteryx.com or leave a comment below!

Let’s dive into this week's quest!

Download the provided JSON file containing your starting data and workflow files.
Upload the provided Cloud Quest 32 Start.json file into your Analytics Cloud library.
All necessary datasets are contained within Text Input tools in the workflow.

For more detailed instructions on how to import and export Designer Cloud workflow files, check out the pinned article Cloud Quest Submission Process Update.

Scenario:

In Alteryx Designer Cloud, continuous numeric values are left-aligned by default, which can make it difficult to visually compare numbers with different digit lengths.

In this week’s Cloud Quest, your task is to reformat the given [Amount] column so that each digit—including the decimal point—is placed into its own separate column, ensuring that all decimal places are perfectly aligned. Each numeric value should have 2 decimal places.

By the end, your output should be a structured table where numbers are visually easier to compare at a glance.

Source: https://www.mashupmath.com/blog/expanded-form-with-decimals

Bonus: Make your workflow dynamic to accommodate any incoming [Amount]. Assume a maximum of 2 decimal places.

Hint: Ensure [Amount] values have two decimal places before counting digit lengths.

If you find yourself struggling with any of the tasks, feel free to explore these interactive lessons in Alteryx Academy for guidance:

Once you have completed your quest, go back to your Analytics Cloud library.

Download your workflow solution file.
Include your JSON file and a screenshot of your workflow as attachments to your comment.

Here’s to a successful quest!

- The Academy Team

Download Start File | Download Solution File

ggruccio · ‎04-02-2025

Got the bonus logic to work!

Spoiler

...but I had converted all values to text to pad them, and then when creating the results by column each digit needed to be converted to a numeric value. Not sure how dynamic I could make the field conversions because the decimal point would not always be in the same field depending on the maximum length of the dataset.

Screenshot 2025-04-02 134752.png

...but I had converted all values to text to pad them, and then when creating the results by column each digit needed to be converted to a numeric value. Not sure how dynamic I could make the field conversions because the decimal point would not always be in the same field depending on the maximum length of the dataset.