ACT NOW: The Alteryx team will be retiring support for Community account recovery and Community email-change requests Early 2026. Make sure to check your account preferences in my.alteryx.com to make sure you have filled out your security questions. Learn more here
Start Free Trial

General Discussions

Discuss any topics that are not product-specific here.

Advent of Code 2025 Day 6 (BaseA Style)

AlteryxCommunityTeam
Alteryx Community Team
Alteryx Community Team

Discussion thread for day 6 of the Advent of Code - https://adventofcode.com/2025/day/6

37 REPLIES 37
Hub119
12 - Quasar
12 - Quasar

Fairly straightforward one today, no macros needed... just some simple clean-up/rearranging of data... now back to enjoying my OTHER Advent Calendar 🥃

Spoiler
AoC 2025 D6 Pic.png
clmc9601
13 - Pulsar
13 - Pulsar

Wow, that was wild. So much slicing and dicing that I feel like a surgeon... but unexpectedly on numbers. Thankful it took less than an hour!

 

 

Spoiler
Embarrassing how much I use the Crosstab tool in Advent of Code, when I AVOID it at all costs in production workflows 😅

Lots of parsing!

2025-12-05_23-41-16.PNG

My part 2 gotchas:

 

Spoiler
  • Read the problem carefully: the leading/trailing spaces are important, and they vary by line
  • Remember to remove the space columns before concatenating the numbers
  • If you end up with zeroes (for example not all columns have a number with four digits), don't multiply by 0 on that row

 

 

Tokimatsu
12 - Quasar

Is this half of it?

Spoiler
スクリーンショット 2025-12-06 144657.png

gawa
16 - Nebula
16 - Nebula

My WF totally depends on fixed data schema of input data and does not have generalizability, but in order to enjoy my Saturday life, I compromised about it.

 

And, many thanks to Alteryx product team for adding "Product" option in the Summarize tool since 2023.2 release. It really helps!

 

Spoiler
image.png
CoG
14 - Magnetar

Another simple problem??? The trickiest part of today was the testing of my reading comprehension.

 

Spoiler
Not my most elegant approach. Threw tools on the canvas, solved three different problems (that weren't was AoC was looking for), based on different readings of the problem statement. After more careful examination, I realized that a full column of spaces denoted the column breakpoint... Whoops.

Otherwise, simple prepping, parsing, and blending of data to get the output!

Screenshot.png

Version 2 (More Elegant/Clearer Design):

Spoiler
Screenshot V2.png

 

Happy Solving!

AkimasaKajitani
17 - Castor
17 - Castor

Just how to parse it!

 

@clmc9601's "Surgeon" metaphor is fun😂 I think so!

 

Spoiler
AkimasaKajitani_1-1765001500828.png

 


 

ScottLewis
11 - Bolide

Got stubborn about working in columns rather than just tokenizing to rows. Ran into the column limit on parse and just bulled through it with substrings. Do not do these things. If you're looking for how to do the thing, look elsewhere today. Your princess is in another castle.

 

 

Pilsner
13 - Pulsar

Day 6 complete, halfway through already?! This problem served as yet another reminder to check the field length on the input tool (one day I'll remember to check first) 😂

 

Spoiler
Here's my full workflow:
Pilsner_0-1765014678690.png

 


Part 1
1) Step one involved parsing the values into their respective columns. Using the regex tokenise, this was easy enough as I could define each group of values as a list of “non-spaces”.

 

Pilsner_1-1765014828792.png

 



2) Next, I  decided to separate the operators from the numeric values. This allowed me to then join back based on the previously created column ID, so that I knew exactly which operation should apply to each number.

Pilsner_2-1765014842066.png

 



3) With the separate operations identified, I filtered to the multiplications and used the summarise tool to find the product of the numbers, per column.

Pilsner_3-1765014867425.png

 



4) All the remaining values (answers to the multiplications and the values that were originally addition) can now be unioned together. By summing the column containing the unioned answers, the grand total can be calculated.


Pilsner_4-1765014879834.png

 



Part 2

My part one and part two are actually begin quite differently to each other. Other than sharing a row ID, the two data streams split almost immediately.


 1) As we now know the cephalopods read numbers vertically, I decided to tokenise each row, at the single character level (spaces included), before assigning a vertical ID.

Pilsner_5-1765014922564.png

 



2) By filtering out the operators, I could then focus on just the numbers. As all vertically aligned values now share an ID, it was a simple case of concatenating the values to find the cephalopods' numbers.

Pilsner_6-1765014958838.png

 



3) Similarly to part one, I then joined the numbers back to the operations, based on the vertical ID. Unfortunately, because the ID was no longer based on the entire “original column”, there were some missing operators. The operators always appear in the first Vertical ID of the column, so a simple multi-row can populate the remaining values.

Pilsner_7-1765014994282.png

 




4) Now, in order to assign the original column ID I used another multi-row formula, which counted up one, whenever it came across a space.

Pilsner_8-1765015007024.png

 



5) The final steps are the same as above, as the multiplications were calculated first, before all the remaining numbers were then summed together to arrive at a grand total.

Pilsner_9-1765015042555.png

 


 

Yoshiro_Fujimori
15 - Aurora
15 - Aurora

My solution.

As always, the assumption in Part 1 does not work in Part 2...

Spoiler
Workflow
AoC_2025_Day6_workflow.png
Labels
Top Solution Authors