Challenge #383: Data Parsing Delight!

[Watermark]

attn: @AYXAcademy 

NOTE: There are exact duplicate records in the  'OUTPUT FILE' .  When you place a "UNIQUE all fields" you'll discover there are only 198 distinct records. 

Kind of a fun challenge. Seems a lot of people used the JASON tool. I didn't recognize it as JASON, so maybe I'll go create a second answer using it. 

As stated above, my reply didn't get 217, but then I tested the provided answer and discovered there were duplicates. Once I factored for that, the results matched. 

See spoiler/workflow for details. 

 

Spoiler

[myastarling]

Here's my solution. I started out using a second JSON parse but it was a little easier for me not using a second JSON parse tool and simply use Regex parse instead.

[JoshuaM]

Originally thought to use the XML parse tool before revising to JSON, pretty simple workflow tho

Spoiler

Couple insights from the conditions:

CRT0 are basically given away for free and comprise the majority of items.

ZKP0 look to be mid-tier clothing price wise, look to roughly spend a grand here.

ZSPR has an evenly distributed pricing rate so should be the best condition. My guess is that these items are assorted clothing made up of different garments.

[bkclaw113]

Always a fan of parsing exercises

[JamesCharnley]

Spoiler

Decent little challenge that

[tammybrown_tds]

Lots and lots of parsing!

[Qiu]

Maybe too many tools.

Spoiler

[Nathan_Barton_]

Spoiler

[The_Rad_Valentina]

What a fun way to see responses from all of you! We have an awesome group of people who are not shying away from this challenge. Great job on use of the Json Tool. I did not think of it initially. Now the big question is, what response would be fastest at running a solution on a big set of data. 

[dougbaron]

I'm getting rusty. unsure how the final is sorted the same as the expected.

Spoiler