Splitting logs

Bug Reports
1

I had just started LOTW and so I put all my logs into 1 so that I could import them there. I tried to split them back apart into my SSB and FT8 again and it is telling me that I am getting a side something error. I tried to take a screenshot of it but ran out of time. Could you help me get these split back apart?

Thanks

AA8TT

1 Like
2

@AA8TT Good Morning,

I’m not exactly sure what your asking. Did you use the LOTW integration to import your QSO’s into WRL or are you just importing via an ADIF?

So you are wanting to split all of your SSB contacts into their own logbook and all of your FT8 contacts into their own logbook?

If that is correct you could create a new logbook and call it ‘SSB’ and then use the QSO manager and use the ‘filter’ button to filter by mode and then select all the QSO’s and then use the ‘move to logbook’ button to select the SSB logbook you created. Then you could do the same for the FT8 contact.

Let me know how you imported these QSO’s and if this is what your are attempting to do

Thanks & 73
Brad K4AZE

3

Sorry I was not clearer.

I put everything into 1 logbook to download to lotw. Figuring I would just separate them back into two separate logbooks after. This is where I ran into the problem.

That is what I was trying to do. I did exactly as you said and filtered ssb and ft8 selected them and when I say move ft8 to ft8 logbook it comes up with the error message. I thought maybe it was because there were more ft8, so I tried the same thing with the ssb which was only 700ish contacts. When I try to move to logbook I got the same error.

4

This is the error I am getting.

(attachments)

Screenshot_20251019_095300_Opera.jpg
Screenshot_20251019_095300_Opera.jpg1080×2400 267 KB

1 Like
5

@AA8TT I see, ok let me create a ticket for you for this and i’ll reach out to the team and have them take a look.

Thanks & 73
Brad K4AZE

1 Like
6

@AA8TT Good morning,

So sorry for the delay in this. We’ve pushed some fixes for this. If you’ll make sure you’re logged in and the do a hard refresh (hold shift on your keyboard and click the refresh button in your browser) this will make sure you’ve got the latest changes. Then you should be good to go now.

Thanks & 73
Brad K4AZE

1 Like
7

Thanks for getting back to me and for the update. I will do that. Very much appreciated.

Mark
AA8TT

1 Like