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 #53: Parsing Report Formatted Data

jssandom
8 - Asteroid

My solution

kelly_gilbert
13 - Pulsar

Such a practical challenge... Haven't we all needed to work with data like this at some point or another!

 

Spoiler
challenge_53.PNG
JoshuaGostick
11 - Bolide

My solution. I've added a data quality check in case the Split to Columns tool is not creating enough columns.

Spoiler
challenge_53.PNG
NilsM
8 - Asteroid

My solution:

Spoiler
AlteryxChallenge53_2.PNG
Kenda
16 - Nebula
16 - Nebula
Spoiler
I decided to just rename the field that comes in so that I can work with that in case the number of dashes changes in the future. Then splitting the data into rows instead of columns should account for any instance where the number of given columns or rows changes. 
53.PNG
jbranaum
8 - Asteroid

My Solution

vsoni
Alteryx
Alteryx

My solution attached! 

ipeng
8 - Asteroid

My solution. This is an easy one. 

mickael_gest
8 - Asteroid

My solution :)

Spoiler
challenge_53.PNG

challenge_53.PNG

JamesMA
Alteryx Alumni (Retired)

Managed to get the logic fairly quickly, judging the number of necessary columns was the tricky part!

 

Spoiler
Week 53.PNG