Hello Andy,
I already tried doing the conversion replace. The issue is that it seems the system first makes the separator a comma before it hits even the transformation file. It seems the logic goes:
Before Transformation: 45678,Pottery Austin, TX
Transformation using OUTPUTDELIMITER: 45678;Pottery Austin; TX
Conversion using JS to replace: does nothing because there is no comma
After the transformation, because it shows everything to the conversion file as a ";", it appears to the conversion file as another "column". Thus, it doesn't convert anything.
The issue is that before transformation, the system decides to make it a comma, thus forcing the transformation to convert every comma to ";", because it seems it just does a find-and-replace of comma to OUTPUTDELIMITER.
And yes, the goal is to be able to re-import the file back into the system, that is why the number of columns matters. (though, in almost every situation of using the data, it would be an issue.)
I used a city, state as an example, in reality, it's not that simple, sometimes it's a list such as "Black, Smooth, Faucet" or something of the like.
It seems it's just a fault in the logic of the Export I guess.
Alex