Original post was closed and last update was that the issue was being sent to the developers. Checking to see if there is an update as I have seen several other posts citing the same issue/error message that have been closed as well with no resolve.
-Cache has been cleared
-Chrome/Firefox/Extensions uninstalled/reinstalled
-Error was discovered for specific scout but is received on any scout/leader/parent
-Both Scoutbook+ and Legacy are open when trying to execute task
Just checking in to see if there is any update
@JasonMeske updates are only given in the change log. As this uses the non-bsa extension it is outside the scope of IT.
The last reply on got on my original thread that has since closed was that the issue was being sent to the developers. Do you know if this email is still monitored or if there is a better way to potentially get an answer to the issue? I’m looking for solutions to an issue that others seem to be having as well
The extension is basically retired at this point is my understanding.
Ok that helps. Just to clarify, at this moment Scoutbook Plus does not have a feature that allows new scouts be added to existing events, other than the “Future” check marks(which did not work, hence the reason for the original post) correct?
@JasonMeske- I just checked my events and our newly joined scout has been added to events post his joining.
To be clear, were the “future” check marks in SB+ ticked before the scout joined, or after?
Future Check Marks were checked off. The issue was noticed with one scout(141976494) so I started going thru each event and adding everyone and noticed the counts for the events going up by more than 1. Thats when I tried using SB legacy with the extension but received the error message which led me to posting here to try to find an answer. I appreciate the help and I will just finish going thru the rest of the events to ensure all of the scouts and family members are aware of events.
The Unit Quick Entry feature allows multiple events to be deleted from scouts, I dont understand why deleting of events was prioritized over adding of events. This really would be a great feature instead of the Future check marks which can be easily forgotten.
Thank you
Issue was noticed with one scout(141976494) and as I looked into it I noticed others affected as well.
The reason I keep trying to clarify is that, if it didn’t work for one or more scouts (but was checked-off prior to those scouts being added to the unit roster), then the automated system failed and needs to be investigated. If the scouts were already in the roster, I think this is the expected behavior. That is, these would be events added after the scout(s) were on the roster to which the scouts were not invited, and therefore the automated system wouldn’t add them as a scout who joined in the “Future”.
I suspect (but have no inside knowledge since I’m just a unit volunteer) that bulk-removing was prioritized over bulk-adding because of the desire to facilitate removal of scouts or adults who have left a unit. I am also guessing that bulk-addition to events was assumed to be covered by the functionality offered by the “Future” checkbox, and therefore de-prioritized (either temporarily or permanently under the theory of eliminating one more feature requiring support).
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
© 2019 Boy Scouts of America - All Rights Reserved
