Log4OM

Hello

I create a new post because my question is "drowned" in the middle of other posts
I am making great strides in the printing of the QSls

I have a problem in the management (Routing)

example : with 3D2AG in my QSL Via field in my Log I have "OQRS Clublog"
but in the "routing" tab it always puts "Manager: FT8"

I therefore suppose that Log4OM does not take into account the value of the "QSL Via" field entered in the log but take this value automatically I do not know where (QRZ.com?)

is it possible to modify this in this "Routing" tab before print ?
I haven't seen anything in the documentation on the subject and I tried to modify it manually but whatever I do it always prints " FT8"
Thanks [/quote]

Thats is the reason for the routing tab so that you can edit any thing that you dont want or is incorrect, just edit the field and move on

BTW if the field is empty it is filled by the on line lookup data like QRZ/HamQTH

Hello Terry
YES I Think
but as I have said :
<
is it possible to modify this in this "Routing" tab before print ?
I haven't seen anything in the documentation on the subject and I tried to modify it manually but whatever I do it always prints " FT8"
>
I modified FT8 to "F6FLU" for example, I validate by clicking on the green tick at the top right
but it still prints FT8 ...

F6FLU wrote: 26 Dec 2020, 09:35 Hello Terry
YES I Think
but as I have said :
<
is it possible to modify this in this "Routing" tab before print ?
I haven't seen anything in the documentation on the subject and I tried to modify it manually but whatever I do it always prints " FT8"
>
I modified FT8 to "F6FLU" for example, I validate by clicking on the green tick at the top right
but it still prints FT8 ...

OK now I understand what your issue is and having checked this out I find we have a bug because even having edited the QSO QSL sent via information it is not reflected in the label print routine because it is being overwritten by on line look up information.

I will move this thread to error reports and add it to our Mantis list

Thank you for finding this bug

OK Terry
thanks ...

That's not possible due to the application design.
QSO with the same callsign are grouped in a single "object" that contains multiple QSO potentially printable into a single QSL.
Those QSO *may* have different QSL SENT VIA status so the application is unable to identify the right one if the status is not aligned.

The "online" way is a way to find the most current address and qsl routing path also for old QSL never sent before, with the mostly accurate information