We're actively looking for ideas on how to improve Weekly Challenges and would love to hear what you think!Submit Feedback
A solution to last week's challenge can be found here!
We are thrilled to present another Challenge from 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 incorrect JSON formatting.
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 is trying to build an app that requires a JSON file as an input. He has created a workflow in Designer to produce this JSON file. The problem? The .JSON file is created but, after opening the file, he notices that it contains backslashes ‘\’ that should not be there (shown in fuschia below). For example:
He cannot use this file to build his app, as it is not the proper format. Even more puzzling? When he reads in the .JSON file in Designer, the backslashes do not appear. What’s going on?
Your Goal: Create an output without the extra delimiter ‘\’.
Asset Description: The co-worker is desperate and has shared the workflow he uses, which includes a workflow (included in the start file).
This was easier than I thought it would be...
Here is my "solution"...
Let me know if I messed it up, and I'll try another approach. (EDIT: I see other people used the same technique, so I feel ok now)