We posted the solution JSON file to Cloud Quest #11. Check it out and let us know what you think! Send suggestions to academy@alteryx.com or leave a comment below!
This week's challenge was inspired by a submission from @pawel_zych. Thank you for your contribution!
For more detailed instructions on how to import and export Designer Cloud workflow files, check out the pinned article Cloud Quest Submission Process Update.
In this week's quest, you are a procurement specialist about to begin negotiations with the suppliers of parts you need for your operation.
Your first dataset contains purchase orders from last year. Your second dataset contains forecasted demand for parts you need in the coming year, paired with the suppliers who can deliver them.
Your task is to create a “Negotiation File” to use while negotiating prices with your suppliers for the coming year. You want to create one record for each part even though you have previously purchased parts from multiple suppliers. Include a column that indicates the contribution percentage of each previous supplier for a given part.
Hint:
Unlike Designer Desktop, the Summarize tool in Designer Cloud does not apply any kind of sorting to its output. You may need to sort your dataset prior to summarizing to get your expected result.
The Round function will round to the nearest value in the multiplier. For Example:
The result of Round( [31.19], 1 ) = 31.
The result of Round( [31.19], 2 ) = 32.
The result of Round( [31.19], 5 ) = 30.
A combination of the Join, Sort, Summarize, and Formula tools should help you create the file, but not necessarily in this sequence.
If you find yourself struggling with any of the tasks, feel free to explore these interactive lessons in the Maveryx Academy for guidance:
Once you have completed your quest, go back to your Analytics Cloud library.
Mine is also having slight difference about the percentage. And there is only one "Round" function so dont really know where went wrong.
The Round function will round to the nearest value in the multiplier. For Example:
The result of Round( [31.19], 1 ) = 31.
The result of Round( [31.19], 2 ) = 32.
The result of Round( [31.19], 5 ) = 30.
I will add this information to the "hint" above.
It looks like the Output Solution in the Start file is using a 2 in the Round function. e.g. Round( [value], 2 ). This seems wrong and explains why some of the percentages add up to more than 100%.
If I change my function to round to the nearest 2, it matches the provided solution.
Comfortable with my solution 😊
Here's my take