I go into the Scoutbook Plus roster, and select “Unit Quick Entry” → “Scout Leadership”
With our COH coming up next week, I wanted to go in and mark every leadership position as ending on that date, and then mark all the new leadership positions as starting on that date. It appears that scoutbook does not support this, which is unfortunate from an auditing perspective, since it makes it difficult to tell the difference between a leadership position that legitimately spanned two terms vs one that I simply forgot to end at the end of a term.
That is not the primary issue however, the primary issue is that when I hit save, it displayed an error that read “Missing required fields or entered invalid values” which is entirely unhelpful since it neither highlighted the “bad” values, nor told me which ones were this issue.
Opening the browser console I was able to see the actual error was
If you have the error right there, why are we not passing that on to the user? That 37900689 number matches nicely with the row key of the problem row in the grid, so highlighting it should be easy enough.
(The problem row is gone now that I corrected the date, but you get the idea)
Also, just want to point out that if Scouting America would just open source Scoutbook I could just fix this myself in an afternoon for free and we would all be better for it.
@Adam-Cramer ok to clearly understand
Scout has Patrol Leader 1/1 - 6/1. Is reelected. So you went in and ended 6/1 and added a new one 6/1? Instead of simply not touching the position?
I see the issue @Adam-Cramer - this is more an issue of IT putting in bad on screen errors - but it is reported.
Yes, my hope was that it would show in their leadership record as two separate instances instead of one long instance
You do realize the length of leadership like this is trivial. As long as the tenure fits for ranks is all that matters.
playing with this it is an API issue I bet - so I imagine they will just change the error message.
the Fix is end position with a date a day earlier - Save - then go back and add the next position. Ex. Go in end position 6/31 > Save > add new position 7/1. If you see the old position on the screen it will fail
@Adam-Cramer
We found an issue where the repeated position error is not clearing thus it will not allow Quick Entry to be used again, hopefully that will clear up tomorrow. This issue has been reported.
The system will not allow a Scout to hold the same position more than once on a given day. If you want to show consecutive terms, you need to end the current on for example 9/1 and start the next on 9/2.
Yeah I noticed that issue as well, I was able to get around it by putting an end date on the still offending rows and then saving and clearing the end date afterwards.
I understand the limitation of not having duplicate terms on the same day. That makes sense to me and I don’t want to suggest that should change, I only included that as replication steps for the error message.
@Adam-Cramer
One thing to keep in mind if you end a position on 9/1 and start the same position on 9/2, these will be reported as 2 separate positions, not one continuous position. This means on an Eagle app, the system could use 2 lines, where it could have used 1 if the position was not ended and restarted the next day.
