While transferring scouts from AOL Den to Troop, I timed out when things got busy. When I got back to it I had to start over. I got the scouts into the troop account and into their New Patrol. Now they showed up again in applications on the troop side after I accepted the original applications. 6 of these 7 scouts are still showing in applications. Now they are showing up again needing to be assigned in a patrol.
When assigned first round into a new patrol, I started in SB Legacy, created a new patrol then tried to “reassign” new scouts into patrol. This took me to SB+. After I got the new scouts into this patrol I now have 2 patrols with the same name. One with scouts and one without. I was able to delete the 2nd patrol from SB+ but it is still showing in SB Legacy. I have tried to follow google’s path to delete from SB Legacy but am not finding their recommended options.
Do I ask the registrar to delete this 2nd set of names off of applications in my.scouting? or?
Do I “end membership” on this 2nd set of these scouts in SB Legacy or is there another route I should take?
How do I delete the 2nd patrol in SB Legacy
These are the scouts and leader in the New 2026 patrol (pending name).
This is what I am seeing SB Legacy. Need to delete this patrol with -0- scouts and end the 5 showing in “scouts not in a patrol(5)”.
This is what I am seeing in my.scouting.
@TammieZemler - DO NOT TOUCH LEGACY SCOUTBOOK. The only things left there are payment logs and tools for merit badge counselors. As far as my.scouting.org.. there is nobody here to help with that so reach out to your council.
So as long as what I am seeing on SB+ looks right, I just ignore SB Legacy?
Looks like we got everything cleaned up. The registrar was able to delete the duplicate applications showing in my.scouting. All the scouts are in their correct patrol and only one showing on the SB+ end. The 2nd patrol is still showing in SBLegacy butt you say not to worry about it.
You say we only use SB Legacy with payment logs and MBC. However when adding these new scouts, the treasurer is not able to see these new scouts. I was not able to find the place in SB+ Function Manager where to add connections for new scouts. I had to go back to Legacy under connections to add these scouts.
Is there something I am missing to do this in SB+? I want to not use legacy but need to know how to do this in SB+. Thanks
@TammieZemler - i did mention the payment logs are still in legacy which is what still needs to use connection manager for MBC and payments logs.
ok, just making sure I was on the right page. Thanks
I know I an not to use SB Legacy however, the same issues mentioned above are happening with the duplicate scouts showing up in the reports and rosters when running reports. The duplicate applications were removed by the Council registrar but still showing these scouts as duplicates in the reports I run in SB+. Yes I can delete them from the reports but when will this stop? Shows correctly in SB+.
The NEW patrol is now Mighty Tacos showing the 7 scouts.
But the 5 scouts who were showing duplicate applications are still showing in “scouts not in a Patrol”. Their duplicate applications have been taken care of on the my.scouting end. Do I just “end membership” on these 5 to get them to go away?
Both locations are showing the same BSA# both show attendance and totin chip and firem’n chit they earned this month. Am concerned that if I end their membership for those in the Scouts not in a Patrol they will disappear altogether. Please advise.
@TammieZemler - how about you stop messing with legacy scoutbook.
@TammieZemler I think this is fixed. Please post the member ID numbers of any Scouts that you still see on your roster more than once.
(No names, please)
@Stephen_Hornak
A Scout is helpful, friendly, courteous and kind.
I was not in legacy until I ran my report in SB+ with issues of doubling up the scouts who I had issues with before. I needed a solution for a problem and you chose to be unkind, unfriendly, uncourteous and unkind.
Thank you to @JenniferOrlinger who actually fixed the problem. The duplicates have disappeared and my reports are running correctly.
