Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

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 #40: Parsing a HTML File

Normster
8 - Asteroid

As I was checking the results I noticed empty records which prompted me to use the Unique tool.  I found 6 duplicate records so my total results are different.  Also kudos to spotting some of those data discrepancies.  (I found one).

 

Normster

Spoiler
Normster_0-1593875952742.png

 

 

attilajozsefhegedus
7 - Meteor

almost there

AnaisComyn
9 - Comet

Done !

Lucatelli
8 - Asteroid

Please find attached my proposed solution.

FlorianC
Alteryx
Alteryx

I would always recommend checking the decoded HTML data in a browser to better understand the structure of the data before jumping into parsing.

 

P.S. For some reason the expected results are missing data when the practice is multiple.

 

Spoiler
WorkflowWorkflow
Florian Carrier
Strategic Solution Consultant
Alteryx
JethroChen
10 - Fireball
Spoiler
challenge_40_jc.PNG
Ben_Jeffreys
8 - Asteroid

My submission

lauren83
7 - Meteor

8th Challenge Complete 🙂

JoePC
9 - Comet

Solution Attached

AkimasaKajitani
17 - Castor
17 - Castor

My solution.

 

Parsing HTML is hard because the pattern is different every time.

 

Spoiler
AkimasaKajitani_0-1599914022727.png