It was my understanding that the LoTW API invoked when you click DXKeeper's "Sync LoTW QSLs" button with the date YYYY-MM-DD shown
beneath this button would report

1. any new confirmations received date YYYY-MM-DD

2. any new grants of DXCC award credit made after date YYYY-MM-DD


In working through the issue that Pete N4ZR raised here

I was informed by LoTW staff that #2 is not correct. When you are informed that the LoTW-confirmed QSOs you submitted for award
credit have been granted that credit, you cannot simply invoke DXKeeper's "Sync LoTW QSLs" function to update your logged QSOs to
reflect the granting of that DXCC credit.

If you use DXKeeper's DXCC Submission Generator to select the QSOs you submitted for DXCC Award Credit, then your submitted QSOs can
be update to reflect their DXCC award credit by clicking the "DXCC Submission' window's "Verify Submission" button. This is steps 7
and 8 in the " Generating an LotW Submission" section of

<>


Note that you also have the option of having DXKeeper download all of your DXCC credits from the ARRL and use this information to
update the DXCC Credit status of all of your logged QSOs. This works smoothly for QSOs confirmed via LotW, but QSOs confirmed via
QSL cards may have slightly inaccurate DXCC credits as a result of data entry errors or shortcuts -- like specifying the correct
DXCC entity, band, and mode, but specifying an incorrect callsign or an incorrect date. Expect 25% of the DXCC credits generated
from QSL cards to require manual "linking" to your logged QSOs. Step-by-step instructions are here:

<.


While it's tempting to make a DXCC submission of QSOs confirmed via LoTW by letting LoTW pick the QSOs to submit, doing so is the
wrong choice for two reasons:

1. LoTW's selection of QSOs to submit is suboptimal; you may submit more confirmed QSOs than are necessary. For example, in need of
DXCC credit for P5 in both RTTY and on 160m (but not on 40m or Phone), LoTW might have you submit a 40m RTTY QSO and a 160m Phone
QSO when you have a confirmed 160m RTTY QSO.

2. You can't use DXKeeper's "Verify Submission" button to update your logged QSOs to reflect DXCC Credit granted with one gesture.

Thus you cannot rely on invoking the "Sync LoTW QSLs" function after being informed that the QSOs confirmed via LoTW that you
submitted for DXCC award credit have received that DXCC award credit to update your logged QSOs to reflect the granting of that DXCC
award credit.


73,

Dave, AA6YQ

So, are you saying we will need to link the credits manually after submitting them using DXKeeper's DXCC submission generator and the QSO's have been granted DXCC credit?

+ That's the opposite of what I posted, Stan.

+ If you use DXKeeper's DXCC Submission Generator and are informed that credit has been granted to each confirmed credit, than one mouse click will "promote" the status of your logged QSOs to "DXCC Credit Granted.

+ What you can't rely on is the "Sync LoTW QSLs" function to perform this update.?

? ? ? ?73,

? ? ? ? ? ? ?Dave, AA6YQ

?

+ AA6YQ comments below

On Wed, Apr 15, 2020 at 09:00 PM, Stan Gammons wrote:

So, are you saying we will need to link the credits manually after submitting them using DXKeeper's DXCC submission generator and the QSO's have been granted DXCC credit?

+ That's the opposite of what I posted, Stan.

+ If you use DXKeeper's DXCC Submission Generator and are informed that credit has been granted to each confirmed credit, than one mouse click will "promote" the status of your logged QSOs to "DXCC Credit Granted.

+ What you can't rely on is the "Sync LoTW QSLs" function to perform this update.?

? ? ? ?73,

? ? ? ? ? ? ?Dave, AA6YQ

?

Bummer that the "Sync LoTW QSLs" can no longer be relied on :(

+ It can be relied on for its original purpose: to update your logged QSOs to reflect their confirmation via LoTW.

+ Note that invoking "Update LoTW Status" on a logged QSO to which DXCC credit has been granted will update that logged QSO to reflect the grant of DXCC credit.

? ? ? ?73,

? ? ? ? ? ? Dave, AA6YQ

?

It was my understanding that the LoTW API invoked when you click DXKeeper's "Sync LoTW QSLs" button with the date YYYY-MM-DD shown
beneath this button would report

1. any new confirmations received date YYYY-MM-DD

2. any new grants of DXCC award credit made after date YYYY-MM-DD


In working through the issue that Pete N4ZR raised here

I was informed by LoTW staff that #2 is not correct. When you are informed that the LoTW-confirmed QSOs you submitted for award
credit have been granted that credit, you cannot simply invoke DXKeeper's "Sync LoTW QSLs" function to update your logged QSOs to
reflect the granting of that DXCC credit.

If you use DXKeeper's DXCC Submission Generator to select the QSOs you submitted for DXCC Award Credit, then your submitted QSOs can
be update to reflect their DXCC award credit by clicking the "DXCC Submission' window's "Verify Submission" button. This is steps 7
and 8 in the " Generating an LotW Submission" section of




Note that you also have the option of having DXKeeper download all of your DXCC credits from the ARRL and use this information to
update the DXCC Credit status of all of your logged QSOs. This works smoothly for QSOs confirmed via LotW, but QSOs confirmed via
QSL cards may have slightly inaccurate DXCC credits as a result of data entry errors or shortcuts -- like specifying the correct
DXCC entity, band, and mode, but specifying an incorrect callsign or an incorrect date. Expect 25% of the DXCC credits generated
from QSL cards to require manual "linking" to your logged QSOs. Step-by-step instructions are here:

<.


While it's tempting to make a DXCC submission of QSOs confirmed via LoTW by letting LoTW pick the QSOs to submit, doing so is the
wrong choice for two reasons:

1. LoTW's selection of QSOs to submit is suboptimal; you may submit more confirmed QSOs than are necessary. For example, in need of
DXCC credit for P5 in both RTTY and on 160m (but not on 40m or Phone), LoTW might have you submit a 40m RTTY QSO and a 160m Phone
QSO when you have a confirmed 160m RTTY QSO.

2. You can't use DXKeeper's "Verify Submission" button to update your logged QSOs to reflect DXCC Credit granted with one gesture.

 
Thus you cannot rely on invoking the "Sync LoTW QSLs" function after being informed that the QSOs confirmed via LoTW that you
submitted for DXCC award credit have received that DXCC award credit to update your logged QSOs to reflect the granting of that DXCC
award credit.


              73,

                 Dave, AA6YQ

Thank you for pursuing this with the LOTW folks, Dave.? Too bad, because it seemed like such a logical step, but maybe they will be motivated to make improvements

+ DXKeeper provides one-click automation for updating logged QSOs to reflect the granting of DXCC Credit:

<

+ Assuming that "Sync LoTW QSLs" would do this was only necessary when the above-cited procedure was not used to create an LoTW submission.

? ? ? 73,

? ? ? ? ? ? ? Dave, AA6YQ

?

?

+ AA6YQ comments bellow

On Thu, Apr 16, 2020 at 04:47 AM, Pete Smith wrote:

Thank you for pursuing this with the LOTW folks, Dave.? Too bad, because it seemed like such a logical step, but maybe they will be motivated to make improvements

+ DXKeeper provides one-click automation for updating logged QSOs to reflect the granting of DXCC Credit:

<

+ Assuming that "Sync LoTW QSLs" would do this was only necessary when the above-cited procedure was not used to create an LoTW submission.

? ? ? 73,

? ? ? ? ? ? ? Dave, AA6YQ

?

?

I understand, Dave, but when you're on the LOTW web page and it tells you that you have 890 uncredited DXCC counters on LOTW and you can "just click here", I'm sure I'm not the first to have fallen into this trap.

+ With that many new DXCC credits, there is a reasonable way to update your logged QSOs to reflect those new credits: depress the CTRL key while clicking the "Sync LoTW QSLs" button.

+ This will direct LoTW to report the status of *all* confirmed QSOs, which of course includes the 890 to which DXCC award credit was recently granted. Depending upon how many QSOs you have confirmed in LoTW, it can take a very long time to run.

+ This operation is primarily provided for new DXKeeper users switching from another logging application whose exported ADIF file does not include LoTW status.

+ The recent changes to LoTW APIs made the ARRL were aimed at stopping abuse of the "report the status of *all* QSOs" and "report the stations of *all* QSLs" capabilties. I hope that everyone reading this will avoid depressing the CTRL key while clicking "Sync LoTW QSOs" or "Sync LoTW QSLs" unless you are a new DXKeeper users making the transition described above, or unless you are in Pete N4ZR's situation of having many hundreds of new DXCC credits that were requested without using DXKeeper's DXCC Submission generator.

? ? ? ? ? ?73,

? ? ? ? ? ? ? ? ? ?Dave, AA6YQ

?