This could be for a couple of reasons. First of all, do you click on "Apply" after you make the change in the tMap? If not, try that. Traditionally you could see a reversal in what you have done in the tMap if you did not apply it before clicking OK. This is not always the case, but it is auto-pilot for me to click "Apply" before "OK" when working in the tMap. Also, your tMap output I assume is linked to the schema of your tFileOutputDelimited. Have you tried changing that schema?
Can you show me the schema of the tFileOutputDelimited. Can you change it (input and output), save it and then open the schema again to see that it is still the same. This should change your tMap schema.
If you change the schema from the tMap you should see a "Do you want to propagate the schema" message. Click yes or OK to this.
Did you follow the advice of my post above? You say that after saving the order changes. Have you tried running the job to see the changes have been implemented before saving?
I am having the same issue in which I have a tfileoutputdelimited going to tmap, going to a tsalesforceout component (update) with log files afterward.Even though the tmap is set correctly, the output has field A's value going to field G, and vice versa. I am mirroring another job with the same set up that is working flawlessly. The mismapping ends up showing in the reject file after tsalesforceout.
Hello, I don't know if you still have this issue, but you can try this as a temporary fix :when you update your schema IN TMAP and change the order, also change something else ( usually I uncheck the nullable field). This will save the changes and you just have to reopen, check back the nullable field, keep the order and save. However i don't know if this is related but when I restart talend, these changes are lost and the order go back to how it was.
EDIT: to help troubleshoot this issue, it seems that the unwanted re-ordering of the columns is done when editing schema through input and not tmap
