We've recently made an accessibility improvement to the community and therefore posts without any content are no longer allowed. Please use the spoiler feature or add a short message in the message body in order to submit your weekly challenge.

Weekly Challenge

Solve the challenge, share your solution and summit the ranks of our Community!

Also available in | Français | Português | Español | 日本語
IDEAS WANTED

We're actively looking for ideas on how to improve Weekly Challenges and would love to hear what you think!

Submit Feedback

Challenge #209: Parsing Insurance Claims

aheikes
8 - Asteroid
Spoiler
Challenge209.JPG
kelvinlaw
8 - Asteroid

Here is my solution:

Spoiler
kelvinlaw_0-1585625453867.pngkelvinlaw_1-1585626307903.png
KevinTang
8 - Asteroid

just write the column names to a reference table should be more efficient, but I challenged myself the parse the column names out, that's when the headache started, anyway, even the workflow is really not elegant, I managed to get the column names out.

RWvanLeeuwen
10 - Fireball

Here's my take on the matter

 

Spoiler
209.jpg


Want to see the batch workflow where all the magic happens?
Spoiler
209 batch.jpg
seinchyiwoo
Alteryx
Alteryx

such a good brain teaser for the week...

 

Spoiler
seinchyiwoo_0-1585650191731.png

 

output:

Spoiler
seinchyiwoo_1-1585650219085.png

 

huynv96
9 - Comet

I created a batch macro to extract data, done!

 

Spoiler
Capture.PNG
AkimasaKajitani
14 - Magnetar

My Solution.

 

Spoiler
209.png




rmassambane
8 - Asteroid

I could have made it better, I guess.

Gon
7 - Meteor

This was really fun. Here's my solution, I put some comments in order to make it more understandable. 

Spoiler
209.PNG
TonyA
Alteryx
Alteryx

Busy week so I didn't have a lot of time to play with this. Here's a quick and dirty solution