My solution!
Saqueador
I started out doing this a particularly dumb way that was in no way/shape/form flexible/dynamic/repeatable... and then suddenly I remembered A Particularly Problematic Parsing Example use case and realized I could borrow from that use case to use Regex pattern building (i.e. counting the dashes in the header lines to determine the number of characters in each field) as a way to find the pattern for splitting up the fields.
I love it when I build something and then answer my own question on Community 3 years later... 🙂
I love it when I build something and then answer my own question on Community 3 years later... 🙂
In the end, this one ended up being particularly fun!
Cheers!
NJ
A head scratcher, but once the column parsing is determined it starts to flow. Solution is dynamic for all field names, no manual assignments.
I tried to make this as dynamic as possible. The only manual config is the Select Rows tools to pick out which rows are from which table and cleaning up one field at the end from the bigger output.
Can't help but think I overcomplicated it. Nothing particular strenuous or mind-bending but it took a long time to configure.
Saqueador
The trick was figuring out that the column sizes are related to the number of dashes in the dash rows. Used a macro just to keep the reused sections of the flow tidy and to prove it is a dynamic workflow.
