Imported QSOs not recognized as worked

[oe1kfr]

Hi !

I have this problem since I am working with log4om. When I import ADIF files from WSJT-X or other programs the QSOs are not correct recognized by the programs, as they are not correct added to the statistics. As you can see in the screenshot for example I worked 3B8 in phone in SSB which I entered manually on 15m and later I worked 3B8 via FT-8 on 20m which was imported via ADIF. If I put 3B8 on 20m again in it shows me new Band which is not correct as I worked it already via imported FT-8 QSO. It is the same with complete new DXCCs. The imported QSOs seem to be not recognized correct in terms of already worked.
They are also not showing up in the staistics.
Am I doing something wrong? Does it differ between SSB and FT-8? Think it is the same with same mode QSOs as well...
THX for help
Rainer

log4om_1.JPG (107.69 KiB) Viewed 2528 times

[G4POP]

If you set up WSJT with JTAlert and followed the instructions for direct logging then all would be OK.

Your issue is as far as I can see from the SMALL screen shot that the country is missing on the FT8 QSO

[IW3HMH]

The "main" issue is clear.
If a software will DIRECTLY write into Log4OM database it will bypass all Log4OM quality checks that are usually made before storing the data into the database.
That means if you save a mode called "QWERTY" directly into DB, Log4OM will have troubles dealing with.
If you don't save a DXCC value, again, Log4OM will not recognize the DXCC.

What you can do is IMPORT the ADIF generated by those software (this will run against quality checks) or ask developers to use available data entry services exposed by Log4OM Communicator.
If data missing is only related to DXCC or other public informations you can also do a QSO MANAGEMENT refresh action against QRZ.COM / HAMQTH services of the new data. This will not provide BAND and MODE informations if missing (obviously)