it’s because names are stored as {{qso.their.name}} when entered explicitly, and as {{qso.their.guess.name}} when retrieved from lookups, which is why you need the {{or ...}}
This is an internal implementation detail that users should not have to concern themselves with, but it is what’s available right now.
Hi both Sebastián and Alan
Thanks for outlining, I have understood the general setup and the export possibilities for “private data” now. Please note that the SOTA Comment field mentioned above, where some show their partner names left to the sent/received reports, is displayed only after logging in to SOTA. This is part of their data protection measures.
Regarding the last hint on the {{or ...}} clause for the partner names: I could apply this, but met “false” for those with no name in both sources. No name at all (omit/nothing visible) would be more comprehensive, but I don’t know the syntax for doing so.
I made available to my Polo installation via a “Callsign Notes” file the 1st names for some callsigns (“HB9ABC, Paul”). Can I even call somehow the names on this file for the ADIF export by expanding this {{or ...}} clause?
Thanks for your support.
Vy 73, Markus
I think i explained this before. No you cannot.
It is a lookup file only
Alan
. . . “explain” is probably a bit optimistic, Alan, hi. I probably didn’t understand it correctly. I supposed that a table that can be looked up for a display can be used also to write the same info into a file. I still don’t see/understand the Chinese Wall between these two ways/types of application.
Vy 73, Markus
Confirmed then.
Because it is part of the original design intent.
I’m sorry you do not understand.
Alan
Thanks, Alan. I understand “design intent”. So it’s a design intent, which I regret, hi.
Vy 73, Markus
You’ll cope I’m sure
Alan
That for sure! 
– but I would’t name it “cope”.
Vy 73, Markus
Not tested, but would something like this help:
{{#if qso.their.name}}{{qso.their.name}}{{else if qso.their.guess.name}}{{qso.their.guess.name}}{{/if}}
{{or qso.their.name qso.their.guess.name}} has the same result
Markus wants {{qso.activenamesfile.firstname}}
Alan
I thought @HB9DIZ was saying that was coming back with false when both were unpopulated?
@M1SDH - Yes, Steve: these marked “false” in the grey box above had no name shown in Polo. This is what I can see, but I can’t see the real content of the two mentioned “name” fields.
Vy 73, Markus
And is there, in fact, content?
Do you have any lookup services enabled?
Is the name(s) in question visible in the name field on the “More” tab of the QSO(s)?
Alan
Do you mean me, Alan? I can only report what I can see. I can check the name field on the “More” tab by looking at it, but I have no technical means to oversee it from a database or code view.
I looked at the name field on the “More” tab for these QSOs in my grey box (repeated above) and saw there the same name or blank (nothing) for a “false” entry.
Vy 73, Markus
ok that’s what was needed - thanks
Alan
