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

hbraunius
8 - Asteroid

My solution attached. I also updated the dates to be in standard date format.

Spoiler
209.png

 

patrick_digan
16 - Nebula
16 - Nebula
Spoiler
patrick_digan_0-1585589425653.png

 

OllieClarke
13 - Pulsar
13 - Pulsar

I might have had to parse some pdfs in my time before

Spoiler
Challenge 209.PNG
Since the table structure was the same, I hard coded the headers for ease of building rather than trying to parse them too
pasccout
8 - Asteroid

My solution

abrouwer
8 - Asteroid

Attached is my solution

 

Spoiler
209 Spoiler.PNG
T_Willins
13 - Pulsar
13 - Pulsar

My solution.  Thanks @Assaf_m for sharing another real world Alteryx solution!

 

Spoiler
Workflow 209.png

 

grossal
14 - Magnetar
14 - Magnetar
Spoiler
grossal_0-1585603104470.png

Such a nice challenge. I thought I could do it with less tools, but 10 Tools shouldn't be too bad.

 

Alex

mbogusz
8 - Asteroid
Spoiler
2020-03-30 17_51_49-Greenshot.png
Garrett
11 - Bolide

Wouldn't it be handy if Alteryx supported reading PDF directly without needing unsupported R or Python code?

JORGE4900
8 - Asteroid

Here I am using the Inception date as a row identifier; trimming the field and tokenizing the new lines makes the parsing easier. I still had to clean the commas after parsing in order to change data types.

 

It is always fun to parse data using REGEX.

 

Spoiler
2020-03-30_15-22-23.jpg