I’m a new PoLo user and loving it. However, I am seeing an odd issue with one of my QSOs this morning. I had a contact with KI5YOO, and recorded POTA Park US-2369. Despite both callsign and park # being US, PoLo recorded the QSO as being with Estonia. Even though I had WWFF unchecked in the QSO details, it had apparently been prefilled with an Estonian WWFF entity. Even after I cleared that entity, PoLo still has the entity locked to Estonia.
Thanks, that’s interesting.
To be honest I’ve never paid attention to that field and notice it is empty and greyed out on all contacts that I open. I have tried to get a value into it by adding a variety of WWFF reference values and can not make any value cause an entry into it. I doubt it is a WWFF reference that has any impact on this.
It is also a field that is ever exported in the ADIF file.
Can you tell us what the value of these 4 fields for this QSO when you export that log?
Alan
Also, Can you tell us what callsign lookups you are using?
HAMDB?, HamQTH?, QRZ? paid or free? etc. and what combInation of these are active?
Alan
I’m pretty close to the default configuration. I have QRZ toggled on but haven’t logged in yet. HamDB is also toggled on.
Will follow up on your other question when I export the log.
From the QSO in question:
DXCC: 291
State: LA
CQZ: 4
ITUZ: 7
==
Also, while logging into my free QRZ account did nothing relevant to this issue, when I logged into HamQTH it correctly re-coded the QSO as USA. While the DXCC field in the dialog may not be exported, it does appear to correspond to the flag displayed on the list of QSOs for the operation, as well as the map view.
Andy AB0YT
OK thanks for reporting this. Try as I might, I cannot duplicate it here.
An immediate fix may be to delete the QSO and re-add it.
It has never been reported before so please let us know if it happens again. It may have bene a data corruption during the lookup.
Alan