+ AA6YQ comments below
sync to LOTW seems to be an all or nothing model.
?
i had a list qso's and the from "add requested",? then did UPLOAD to LoTW.? ?The entire signed block of QSO's fails because ONE of them is already in LOTW.??
?
is it possible to "sync requested to lotw, report on failed Q's but accept the balance of the others? on the list that did NOT fail " ???
?
+ If you upload your QSOs to LoTW from DXKeeper, it will never be the case that "Add Requested will populate the QSL Queue with a QSO that has already been submitted to LoTW.
+ If you upload a QSO to LoTW using some other application, and don't change that logged QSO's "LoTW QSL Sent" item in DXKeeper to to 'U', then?
Add Requested" will add that QSO to the QSL Queue, and when you invoke "Upload to LoTW", TQSL will reject the entire batch of QSOs in the QSL Queue because of the presence of that one QSO that was already submitted. We modified TQSL to work this way in 2013 because many ops (not DXLab users) were resubmitting all of their logged QSOs each time they made a few new QSOs. So we equipped TQSL with a database to keep track of each QSO that its user has submitted to LoTW, enabling it to reject any batch that contains an already-submitted QSO.
+ To correctly avoid this situation, either use DXKeeper exclusively to upload your QSOs to LoTW, or if you use another application to upload some QSOs to LoTW, update those QSOs in DXKeeper to reflect the fact that they've already been submitted to LoTW.
? ? ? ? 73,
?
? ? ? ? ? ? ? ? Dave, AA6YQ
