After using the Text to Columns tool, I generally find myself using a Select tool to get rid of the original field that I split up. Could an option be added in the config to automatically delete this field once it is split to columns?
I like the idea @Kenda, but I wonder if embedded selects make the process run slower (microscopically). My observation is that selects create memory/disk versions of the data (depending upon amount of available memory). I tend not to add too many selects in the workflows. I do agree that this is a reasonable ask.
Thank you for posting to the Alteryx Community! We like your idea but can't put it on the road map at this time. But we'd like to keep this idea in mind for when or if we can apply it to the road map.
To me this is a no-brainer, and this suggestion has come up in different forms as well.
While it's often just inconvenient to have to have a Select Tool after splitting to columns, you can completely blow up your flow if you parse to rows, because you're multiplying the data times the number of seperators in a field, and with .dsv/.csv responses from a Download Tool, this can be thousands.