We're actively looking for ideas on how to improve Weekly Challenges and would love to hear what you think!Submit Feedback
Last week's challenge can be found here!
We are thrilled to bring you the first Challenge of our “Think like a CSE” series, brought to you by our fearless team of Customer Support Engineers. Each month, the Customer Support team will ask Community members to “think like a CSE” to try to resolve a case that was inspired by real-life issues encountered by Alteryx users like you! This month we present the case of the missing tool.
Below, we’ve provided the information that was initially available to the Customer Support Engineer who resolved the case. It’s up to you to use this information to put a solution together for yourself.
The Case: A co-worker builds a workflow and shares the YXMD (workflow file) and a YXMC (macro file) with a colleague. However, when the colleague attempts to open the workflow, they receive a message stating “This workflow references macros that are missing or inaccessible. Saving this workflow will permanently disable these tools”. Can you resolve the case?
Explanation of the Problem: A co-worker emailed me his workflow on Friday night along with a macro he created right before he left for a long vacation, and he’s gone somewhere that he doesn't have access to email so I can't get him to package the workflow for me. My co-worker needs me to run the workflow while he’s gone and provide my manager with the (very important) report output that comes out as a PDF. When I opened the workflow to run it on Monday I received the following message:
This (very important) report is due in my manager’s email in 24 hours! Can you help me fix the workflow in time?
|Reporting_Workflow.yxmd||Workflow file that needs to be run to generate the report.|
|AstronomyPictureOfTheDay.yxmc||Macro file that pulls data from an API.|
Bonus Question: My manager has also asked that the specific configuration for the macro is restored to its original values, as there’s a specific date and API key we wish to use. Can you help me to get this working while retaining the original configuration information saved in the macro?
Video Solution (Posted 3/5/2018):
ah, the perks of working for customers and having seen this exact case a bunch of times before :-)
nice practice to keep the skills sharp
Another fun challenge. Here's my solution. Solved for the bonus but I can't for the life of me see how to use the original API key -- it looks to have been masked, so is this even possible?
Solution below! I also ran it with today's date, just for kicks, to see what other sort of results could be seen... Gorgeous! Now this is an app I could really get behind... :)