Start Free Trial

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

Challenge #7: Download Data and Parse JSON

jrlindem
12 - Quasar

Joining the party late, so I also leveraged @TGreen‘s provided API link.

 

If you simply need the link without having to download the revised start file, here it is (as of 2025.10.24):

 

Here’s my workflow solution:

 

Spoiler
jrlindem_5-1761333829772.png

 

 

Here’s a detailing of what I did:

 

Spoiler

I preserved the original [URL] for reference but added the new one in with a label to differentiate.  Having done that, I needed to FILTER to choose the right one.

 

jrlindem_0-1761333785789.png

 

 

 

Next, I jump into the DOWNLOAD and JSON-PARSE and leverage the provided [URL] field:

 

jrlindem_1-1761333785790.png

 

 

JSON data differentiates records and columns numerically, so plucking those values out of the JSON_Name string can be done in a few different ways, but I simply replaced the ‘datatable.data.’ string leaving me with the #.# and then used TEXT-TO-COLUMNS to split at the period.

 

jrlindem_2-1761333785792.png

 

 

Next up, was grabbing only the data fields, found to be JSON ID values of 0-4.  A simple CROSS-TAB later and the data is now in a useable format.  The lower stream is isolating the Field Name values and using those to positionally rename the fields from the actual values.

 

 

jrlindem_3-1761333785795.png

 

 

In thinking about the renaming, I had the [record] field to contend with.  It’s in the upper stream and I could have used a formula and added it in or added union with a placeholder value for the lower stream to match, but by moving the [record] field to the end, past the *Unknown fields; it’ll still work in the DYNAMIC-RENAME.  It’ll throw a warning, saying there is not enough values to fully rename (which is on purpose) and then simply retain the original name.

 

Clever?  Sure.  Best practice?  Maybe not

Hope this helps other late comers to this challenge.  Workflow attached for reference.

 

Cheers, -Jay