Problem: Sometimes when exporting, users may notice their selected output fields appear in a different order in the final exported file than the order they are selected on the output tab of the export.
Current unacceptable solution: Remove the fields from output and re-enter them, OR Re-create the export.
Now, imagine reading that solution after you've spent the afternoon working on an export, creating a replacement header row (since the export doesn't use plain-English field names), only to find the next export file to be all scrambled. How about fixing this problem, instead of telling us to do our work over and over?
I've had this problem several times and the official answer is to recreate the export. that shouldn't be considered a permanent solution.
@Joshua - Same here. I have some starter exports so that we don't have to recreate every single mailing list or whatever. We also then to look at what we exported last time and "save as" for changes. So having to recreate defeats the purpose.
This happens quite often to us. It is very frustrating especially for our exports that are set up to be imported into our phonathon system once they are exported. It works fine for months and then when we go to load our phonathon data, it errors out because the columns have been switched around!
Agree with everything that has been said. So, So, SO frustrating.
I have never had it work to remove fields and then add them back again. Only solution - which isn't really a solution - is to recreate the export. That is maddening.
Ditto Karen - removing and reentering doesn't fix problem and for many of my exports it's way to much work to recreate and then not even be guaranteed that problem will not be recreated.
I agree with what everyone is saying. It is not acceptable to tell me to recreate the export to fix the problem. This has caused many hours of headaches to recreate exports just b/c the fields come out in the wrong order. Please fix this bug.
@Jenn - Any word on a solution to this issue?
I hope there is a solution soon to this!
Waiting for a solution to this one for sure!
This happens to my exports. I don't understand how recreating something I just created would solve the problem, and I don't want to waste my time doing that if it might not work.
Any update? This is frustrating . . .