DXLab@groups.io | modifying logged QSOs that have already been submitted to eQSL or LoTW

Dave AA6YQ

#197046

The corrective actions suggested in the message below are incorrect. The appropriate actions are

----------------------------
Correcting the first situation:

1. right-click the Log Page Display entry for the QSO, and select "Upload to LoTW" from the popup menu.

2. wait a few minutes for LoTW to process your submitted QSO

3. right-click the Log Page Display entry for the QSO, and select "Update from LoTW" from the popup menu.

Correcting the second situation:

1. right-click the Log Page Display entry for the QSO, and select "Upload to eQSL" from the popup menu.

2. wait a few minutes for eQSL to process your submitted QSO

3. on the Main window's QSL tab, 

3a. set the "QSL Via" panel to eQSL.cc

3b. click the "Update from eQSL.cc" button

----------------------------

The above information will appear in the reference documentation updated with the next version of DXKeeper, as well as in "Getting
Started with DXLab" after the next version is publicly released.

          73,

                Dave, AA6YQ

Show quoted text

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Wednesday, October 28, 2020 7:26 PM
To: DXLab@groups.io
Subject: [DXLab] modifying logged QSOs that have already been submitted to eQSL or LoTW

If you modify the callsign, QSO begin, band, mode, submode or station callsign item of a QSO that has already been submitted to
LoTW, then when you later invoke a "Sync LoTW QSLs" or "Update from LoTW" operation in which LoTW reports the confirmation status of
that QSO, DXKeeper will be unable to locate that QSO in your log. As a result, the dreaded "no matching QSO in log" message will
appear in the after-action report.

Similarly, if you modify the callsign, QSO begin, band, mode, or submode item of a QSO that has already been submitted to eQSL.cc,
then when you later invoke a "Sync eQSL.cc QSLs" operation in which eQSL reports the confirmation status of that QSO, DXKeeper will
be unable to locate that QSO in your log. As a result, the equally dreaded " no QSO matching callsign, band, and mode" message will
appear in the after-action report.

Correcting the first situation is easy: right-click the Log Page Display entry for the QSO, and select "Update from LoTW" from the
popup menu.

Correcting the second situation requires a sequence of 3 steps:

1. on the Main window's QSL tab, set the "QSL Via" panel to eQSL.cc

2. right-click the Log Page Display entry for the QSO, and select "Add entry to QSL Queue (eQSL.cc)" from the popup menu

3. on the Main window's QSL tab, click the "Upload to eQSL.cc" button

These corrections are straightforward for a handful of QSOs, but if you have many "modified after uploading" QSOs in your log and
there's no way to select them all with a filter, correcting them one at a time won't be much fun.

To prevent this from happening, I have extended the next version of DXKeeper with a new "Prompt on change to logged QSO already
uploaded to eQSL.cc and/or LoTW" option in the Options panel on the "QSL Configuration" window's General tab. When enabled (as is
the case by default), the first modification of the callsign, QSO begin, band, mode, or submode item in a QSO already uploaded to
eQSL.cc,  or the first modification of the callsign, QSO begin, band, mode, submode or station callsign item in a QSO already
uploaded to LoTW will display a reminder to re-upload the QSO after all changes to the QSO have been completed and saved.

      73,

              Dave, AA6YQ

--
This email has been checked for viruses by AVG.
https://www.avg.com

Dave AA6YQ

#197045

If you modify the callsign, QSO begin, band, mode, submode or station callsign item of a QSO that has already been submitted to
LoTW, then when you later invoke a "Sync LoTW QSLs" or "Update from LoTW" operation in which LoTW reports the confirmation status of
that QSO, DXKeeper will be unable to locate that QSO in your log. As a result, the dreaded "no matching QSO in log" message will
appear in the after-action report.

Similarly, if you modify the callsign, QSO begin, band, mode, or submode item of a QSO that has already been submitted to eQSL.cc,
then when you later invoke a "Sync eQSL.cc QSLs" operation in which eQSL reports the confirmation status of that QSO, DXKeeper will
be unable to locate that QSO in your log. As a result, the equally dreaded " no QSO matching callsign, band, and mode" message will
appear in the after-action report.

Correcting the first situation is easy: right-click the Log Page Display entry for the QSO, and select "Update from LoTW" from the
popup menu.

Correcting the second situation requires a sequence of 3 steps:

1. on the Main window's QSL tab, set the "QSL Via" panel to eQSL.cc

2. right-click the Log Page Display entry for the QSO, and select "Add entry to QSL Queue (eQSL.cc)" from the popup menu

3. on the Main window's QSL tab, click the "Upload to eQSL.cc" button

These corrections are straightforward for a handful of QSOs, but if you have many "modified after uploading" QSOs in your log and
there's no way to select them all with a filter, correcting them one at a time won't be much fun.

To prevent this from happening, I have extended the next version of DXKeeper with a new "Prompt on change to logged QSO already
uploaded to eQSL.cc and/or LoTW" option in the Options panel on the "QSL Configuration" window's General tab. When enabled (as is
the case by default), the first modification of the callsign, QSO begin, band, mode, or submode item in a QSO already uploaded to
eQSL.cc,  or the first modification of the callsign, QSO begin, band, mode, submode or station callsign item in a QSO already
uploaded to LoTW will display a reminder to re-upload the QSO after all changes to the QSO have been completed and saved.

      73,

              Dave, AA6YQ