Someone described earlier this TT behavior as "ill conceived and poorly executed". Very true. We all expect the multiple imports to behave just like copying a few files from one folder to another: if a file already exists in the destination folder, ask me whether to overwrite it or leave it as is and continue to the next file in line.
As a career software engineer, I would say this part of TT "escaped from the lab" as opposed to being "properly released".
That said, I CAN see some of the TT rationale related to multiple imports. Let us remember that TT assures us the return will be correct or they promise to make it right, implying they might have - at the extreme - to compensate us for duplicate data that leads us to pay unnecessary taxes. Someone at TT MIGHT have told the engineers to make sure that imports never result in duplicated data. Fair enough... but some engineer(s) might have taken the lazy way out: removing previous imports achieves this goal. Clearly illogical, but what the heck, they achieved the requirement AS STATED.
All this is just guesswork and conjecture from a SW engineer who has been around this block more times than I care to count... Bottom line for us = will TT realize the acute problem and fix it quickly enough, in time for filing this year.
