A scout earned his Life rank at today’s meeting (11/18/2024). However the scoutmaster put it into scoutbook as having his BOR on 11/19/2024, but approved on 11/18/2024. For some reason scoutbook allowed this date to be entered even though it hadn’t happened yet. The rank was also then marked completed and leader approved. So now his rank shows as being earned on 11/19/2024. I tried to go in and correct the incorrect date for his BOR but scoutbook wont let me change that date as the rank is marked complete. I then tried to go and unmark the badge approved but it gives me an error as the earned date needs to be todays date or before. If I then try to change the earned date, it gives me an error that I cannot change the date as the BOR date would be after the date I am trying to enter. So… this has to be a bug right? It let an incorrect date be entered, if I try to fix it at the requirement level it throws an error saying that I cannot make changes to a completed rank, if I try to “un-complete” the rank it throws errors either saying that I cannot have a complete date after the current date or it tells me I cannot change the complete date as there is a later date at the requirement level.
I would try to change the date again today since it is now 11/19/24. We will investigate being able to enter a future date for rank. You are correct, this is not supposed to be allowed.
@AdamBauer1 what time where these actions taken so I can test tonight?
Can you give us the BSA Member ID (no names) so the developers can investigate further? If you have not already, please do not make any changes to this Scout’s life rank so the developers can investigate the current status. We will let you know when it is OK to fix the date.
@DonovanMcNeil I would say sometime between 9 and 10 pm is when I was trying to update the scout.
@edavignon Here is the information for the scout in question.
SB User ID: 1111152
BSA Member ID: 133377695
My speculation: the Scoutmaster probably clicked on the “Today” button for the date.
Well, if the scoutmaster hit “today” on the 18th and it put the date down as the 19th that would still be a bug would it not??
Also, your speculation still ignores the whole trying to fix the issue in location 1 says it has to be fixed in location 2 but then going to location 2 says it needs to be fixed in location 1.
@AdamBauer1 I agree. I think it is a bug.
If you could wait before fixing things for this Scout, we would appreciate it.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
