QSO_DATE_OFF incorrectly logged

[KZ3L]

As reported in this thread,

Trying this out to catch up paper log

The QSO_DATE_OFF issue is definitely a bug.

…the QSO_DATE_OFF records the date (in UTC) the log entry was made instead of the actual QSO date.

This works properly while logging real-time, but when entering paper logs into HAMRS after an activation, HAMRS should set the QSO_DATE and the QSO_DATE_OFF to be the same.

Added: This was reported several months ago but the thread automatically closed 14 days after it was posted.

ADI qso_date_off is incorrect

I just created a logbook for an old activation and submitted it to the POTA regional coordinator. Despite reviewing the ADI file multiple times, I did not catch that the qso_date_off date field was set to today’s UTC date - the UTC date I exported the ADI. The logbook file name and date of the QSO is from February. There’s just one QSO in the log. I’ll have to wait to find out if the log is rejected. This is my first submission so hopefully I get a pass. I don’t see this field in the HAM…