I've read a few threads on this site that talk about the difficulty of setting up import mapping. Well, it's more like ranting.

Nobody, however, has addressed how to make it easier. When mapping fields, the target field you move up or down in the order swaps its position with the field that it is replacing. For instance, if I move a field in the 50th position in the target field list to the 2nd position, the field that was #2 is now #50. This is horrendously difficult especially in those cases where most of your fields are off by one or two positions but you have to move some lower down field up.

I know I'm not explaining this very well but I expect everyone understands what I'm trying to describe. We've all been there, done that.

Finally, my question. Has anyone worked out a workflow, a pattern, a system, for lining up source and target fields with a minimum of trips up and down the list of fields? Do you start at the bottom and work your way up? Or is it less disruptive and irritating if you start at the top? What about swapping fields mid-list?

Like many others who have vented their frustration with this process, I just spent hours mapping an export/import. It's not broken. I haven't added or removed fields that would change the order. Yet. But I have several other processes that I'm setting up and I'm not looking forward to spending even more hours mapping import fields again. And again. And maybe again.

I'm really hoping that one of the experts on this forum has developed a workflow to minimize the angst.

As always, thanks in advance for any and all help.

Import works sweetly if the names match.

If they don't then the import can be saved and the order will be restored.

The real problem is that the saved order gets screwed if fields are deleted from the table. This is unfortunate.

Don't we wish that matching field names could always be the case!! And, personally, I do save all my import mappings as scripts, just in case. Even if I don't expect to have to repeat them. But I'm looking at 3 or 4 more, different imports to map.

It's just the initial job that's sooooo awful. That's just my humble opinion.

Still no suggestions from anyone on how the mapping should flow to minimize the tediousness?