POTA Award Refs Update stops POTA ID in "Note" field

[KI5IO]

V 2.33.0.0

When doing an update of the latest POTA Refs (via csv file) via the Award Manager routine all works well for the import/update.

However - once completed Log4OM no longer will recognize the POTA ID in the Cluster "Note" field. Thus the Awards (F3) POTA does not get "auto-filled".

I can resolved by unlocking, deleting the POTA award. Once that is done a restart of Log4OM is needed followed by an update of the Log4OM Awards. Once that update is completed another Log4OM restart is needed.

Then the POTA IDs in the Cluster "Note" field will be recognized and auto-filled to the Awards (F3) tab.

Albeit the most recent refs won't be available except for each, individual manual addition or entry with making the QSO.

Something happens to the POTA award structure when one tries to do the complete POTA Ref update via the csv file.

Not a huge deal, but sometimes can be frustrating when work stations at the newly added POTA sites.

[G4POP]

Did you try a merge instead of a straight import?

Both ways work for me but the merge might serve you well

[KI5IO]

Terry,

Tnx for looking into & testing.

I've tried both merge and direct for the POTA Refs from the CSV file.

I've also tried on two different versions of Log4OM and on two different PCs. One with W-11 and one with W-10.

Once I save the POTA award after the Ref update the the POTA IDs in the cluster are no longer active and thus won't 'autofill' when the spot is selected.

I have to unprotect the POTA award, delete it and then have Log4OM update the awards to get this back to functioning for the POTA ID in the cluster spot.

Not sure exactly what happens, but something stops working (for me anyway) after I update the POTA Refs.

Seems when some OMs add some more text Log4OM does not recognize the POTA ID.

Noted that some PR sites note being recognized either and I've not worked that noted site. Maybe because I'm located in USA?

CA POTA spots do highlight as being recognized by Log4OM so not sure why PR would not also be recognized.

.

[G4POP]

Clearly if the spotter does not include the reference in the correct format we cant recognise it

US POTA 422 means nothing

POTA US-422 is correct way or just US-422 - we are searching for a match to the reference list

I dont understand why the PR-0041 is not highlighted - Not sure if we still highlight if ref or station was already worked I will check.

I will try using same cluster server as you and see if that emulates the issue

[G4POP]

OK finally got Hamalert to recognise me and have run it since early this morning - So far not one missed POTA in Notes/highlight/insert ref in qso

Will leave it running for 24 hours and see what results I get

[G4POP]

Just had one POTA not highlighted in cluster but it was because it is not a reference in the POTA database

BTW I am using the latest list downloaded and imported last evening

[KI5IO]

Terry,

Good to hear and I know those other 'one off' POTA sites are due to the extra verbiage in the Notes field. I've seldom seen those so are likely just some OMs way of adding the data.

I'm still stumped at the Ref import/update causing Log4OM from recognizing the POTA IDs once I complete the update.

I'll go over what is in the U.G. again and also take notes of all my settings just in case I'm changing some parameter/option that is toggling the hiccup I'm experiencing.

Tnx for the look.

[KI5IO]

Terry,

I carefully followed the field assignments and did a POTA Ref csv file update and it went off without a hitch.

However the POTA ID in the Cluster Notes field stopped working.

I also happened to look at the POTA Award Status and nothing will appear. All other awards (including IOTA, SOTA, etc.) appear just fine.

I did a rescan of award refs to no avail.

So I deleted the POTA award that I had just updated the Refs on and d/l'd a fresh file from Log4OM and the POTA IDs are again recognized and the POTA Award is working again.

Bottom line is that something happens when I do the POTA Ref csv update.

As I noted in an earlier comment I've tested this on multiple versions of Log4OM and on two different PCs with both W-10 and W-11.

Not sure if a Debug or Trace log level might show something or not, but I might give that a try as well.

[G4POP]

I thought I had trapped it a short while ago but then I noticed the spotter used a US ref for a Dutch station, see below

Using the same servers as you Nolan

Screenshot 2024-08-03 132052.png (5.17 KiB) Viewed 6123 times

[KI5IO]

I've noticed that a lot from OMs posts on k4zkf or any of the other ve7cc associated clusters. They don't all follow the basic/expected format of US-123456 ...

At least most (close to all) of the posts from the hamalert cluster do follow the expected format. For both POTA and SOTA.