This may be an operator error on my part and not a bug but I’ll detail what it appears to me has happened and hopefully someone can educate me or confirm that it’s a bug or feature issue.
A brief bit of background to explain what I think my issue is:
I was licensed as KC1PVO back in 2022 and setup an LOTW account back then so my LOTW login name was KC1PVO. In 2023 I acquired the vanity call sign NE1NH. I tried to change my LOTW login to match but ARRL IT told me that was not possible because the prior owner of that call sign was still using it as his LOTW login and I had to stick with KC1PVO as a login name.
Fast forward to the present where I have now started to use WRL logging:
This week I setup LOTW integration in WRL and entered my login and password as required. After the import from LOTW was done it appeared to only have pulled in my KC1PVO log entries. WRL showed that the most recent LOTW import record was dated 7/12/2022. That’s the last KC1PVO entry date.
It appears that none of my NE1NH entries came over with the integration. To pull those in I logged into LOTW and did a manual export of the NE1NH entries to an ADIF file and then did a manual import of the file.
As a test I uploaded a new test NE1NH log entry to LOTW via another logging program and have been trying to import it using the WRL Import new QSO’s from LOTW function but nothing newer than 2022 has come over.
With a call sign of NE1NH but an LOTW login name of KC1PVO how do I get LOTW to properly integrate without manual intervention?
Sorry you’re having some trouble. With this unique of a situation I’m honestly not sure as it is based off callsign. If your QSO’s are in your QRZ account I would HIGHLY suggest importing from there vs LOTW for a few reason. The main being LOTW is known to strip certain data such as RST information and their API is extremely old and hasn’t been updated (with no signs of this happening). I think the best alternative solution in this use case would be to just use the QRZ import integration to import from QRZ.
If for some reason your QSO’s aren’t in your QRZ account you could export from LOTW, import into QRZ then use the QRZ integration to import into your WRL account. A bit tedious but would probably be the best solution here.
@K4AZE Brad, does WRL recognize the contact confirmations from QRZ and/or LOTW or are confirmed contacts based on WRL only? If WRL only then not getting LOTW data is no big deal. If WRL does take LOTW confirmations into account then I would be loosing those, yes?
@NE1NH Yes we pull confirmations from qrz and lotw as well as wrl confirmations but it has to be manually triggered via the QSO manager. There is a ‘re-check confirmations’ button. Once you added your lotw credentials and qrz api key you can then re-check for confirmations. You dont have to import from LOTW though.
Here is a screen recording explaining this a bit better:
@N2FSM if you have contacts that are confirmed on both qrz and lotw you will only see the qrz confirmation. same if you have contacts confirmed on wrl and qrz you will only see wrl.
and not a bug but I’ll detail what it appears to me has happened and hopefully someone can educate me or confirm that it’s a bug or feature issue.