Page 1 of 1

Missing comma in SOTA CSV export

Posted: 21 Apr 2014, 18:09
by VE2DDZ
Hi,

I just used the new SOTA CSV export feature and it worked well for me, however I noticed what I think is a bug. The last three fields exported in the v2 SOTA CSV format are
CALLSIGN, SOTA_REF, COMMENT
1. Currently when both SOTA_REF and COMMENT are blank Log4OM exports the line ...., CALLSIGN - no problem

When COMMENT is blank Log4OM exports the line ...., CALLSIGN, SOTA_REF - no problem

When SOTA_REF is blank, but COMMENT is not (for example for an activation), Log4OM exports the line ... , CALLSIGN, COMMENT - which is misinterpreted when uploading to the SOTA database site. The export should be ... , CALLSIGN,,COMMENT to be correctly interpreted by the SOTA database upload.

2. The second item I have is not a bug. For the final field of the upload, currently exported as the ADIF COMMENT field, I wonder if QSL_MESSAGE or NOTE might be more suitable, since once in the SOTA database it can be read by anyone. Since different operators use COMMENT/QSL_MESSAGE/NOTE for different purposes perhaps if it was user configurable might be nice.

Re: Missing comma in SOTA CSV export

Posted: 21 Apr 2014, 18:13
by G4POP
That's strange because VK1DI Ian tested this and found it worked fine, I will have another check on it

Re: Missing comma in SOTA CSV export

Posted: 22 Apr 2014, 14:13
by IW3HMH
Issue found and fixed.
Thanks for reporting.
We will evaluate if release an updated DLL without need to wait for next release