I’m an Assistant Scoutmaster for Troop 328 with the Key 3 Delegate role.
I used Scoutbook+ to create a new patrol “Radioactive Creepers” and moved 5 scouts into this patrol. This succeeded. I then deleted the 2 previous patrols that have been merged into this new one, leaving 1 scout unassigned. At this point, all patrols and the 5 scouts assigned to it disappeared from the roster view in Scoutbook+.
Viewing the same Troop 328 roster from legacy Scoutbook, the new patrol exists and has the correct members. However, 3 of the 5 scouts also appear in the “Scouts not in a Patrol” list, in addition to the 1 that should properly be listed there. Those 3 scouts appear with duplicate entries in the main Troop roster in legacy Scoutbook.
It seems that something in this sequence of actions triggered a bug related to the relationship between scouts and patrols, leading to two different forms of incorrect behavior in legacy Scoutbook and Scoutbook+.
I’d appreciate some assistance in correcting whatever bad data condition has been created here. Thanks!
Edit: Note that https://api.scouting.org/organizations/v2/units/C026782B-23C0-4ECB-BAA2-FD86F2761AA5/youths and https://api.scouting.org/organizations/v2/C026782B-23C0-4ECB-BAA2-FD86F2761AA5/orgYouths both respond with a reasonable set of data containing all of the expected scouts, and this includes what look like correct references to the new patrol by ID and name. https://api.scouting.org/organizations/v2/units/C026782B-23C0-4ECB-BAA2-FD86F2761AA5/subUnits?swCache=true also includes the new patrol as expected. These requests were observed in browser dev tools while viewing the Scoutbook+ troop roster page.



