Generated a purchase order today (01/11/2026) to email to my local scout shop. It lists the date as Created: 2025-11-10…?
Not going to be an problem for sending in my needed awards but may be a sign/symptom of other underlying issues.
@JacobSponsel- its a po… dies not really matter
In regards to the PO itself I agree, it doesn’t matter.
However, with the number of bugs that I’ve seen posted about and the issues I’ve encountered, I’d say that it might very well matter overall. I’m not a coder or programmer by any means; but I know enough about computers to be aware that if the system is generating incorrect dates there is an issue somewhere. Wrong dates here could correlate to any number of other things depending on how the system is set up to work or not at all. Its all just 1’s and 0’s and that’s literally what got mixed up on my invoice date 
.
If its generating this date incorrectly then maybe the system is reading or interpreting Scout birthdays wrong and booting them out of a den for being the wrong age…
Maybe Scout ID #’s are getting mixed up and people or getting place in the wrong pack, district, etc…
Maybe someone’s renewal date is being generating wrong and they loose access…
At the very least someone who knows the system programming should look into it I think.
Unless you’re actually seeing something like that, please don’t suggest it. The developers and SUAC volunteers have limited time, and any time spent on red herrings is time that is not spent on actual bugs.
A report generation date is generally reflecting when an operation is actually executed. For example, I believe the PO date corresponds to when the PO was originally opened (or the earliest “Completed” item on the PO, whichever is earlier). I don’t know if that’s the intention, but that’s what I’ve seen on the past. It’s not reading a database value (like DOB or other things you’re citing).
Both of these items live in a separate database, and are read, not generated by anything directly related to SB/SB+. Rather, SB & SB+ read those values from that registration database. In fact, the folks who support those systems (i.e. everything other than SB & SB+) only take bug reports from council staff, so you would need to report such errors to them, to then be escalated to national for review.
Again, please don’t randomly suggest things are or may be wrong without any substantiating specific examples. All it does was is needlessly muddy the waters.
What is the PO #?
Respectfully, I disagree with some of your take. While I do understand your concern of causing unnecessary worry, here is my point of view,
Yes, I made some “extreme” potentially possible examples about a computer database system to make a point. I did not suggest these things were actually happening or say they were issues that needed to be looked into.
Unless the developers are volunteers also I would think it is part of their job to look at an issues and see if it is having any other unintended affects. My intent was to show that just dismissing a bug/error because it “doesn’t matter” could have unknown consequences and the solution to one issue may solve another. That may not be the case here but I don’t know that, the person looking into it should. Also, we are all volunteers with limited time that we are giving so dismissing someone’s concern is wasteful too.
I just started in my position as Unit Advancement Chair over the summer and got access to SB/SB+ in Sept/Oct. I spend hours and hours cleaning up old awards and advancements because the previous person used SB Legacy for everything. I therefore know that every month it was cleared out and all items were marked as awarded. So I guess this could be possible if it saved over as an empty PO from a previous date when I was learning to navigate SB and then just added things back on to that. Everything on this PO was from December den meetings.
I figured these items are read from a database, but if the SB+ system had an issue with its date then it would misinterpret how it handles the dates it reads off a database.
So again, yes, I made some extreme examples really just to say I would like it if my concern was addressed and not just dismissed, even if it is misplaced. I also hope that someone actually addressing it and familiar with the system would take the time to fully read any comments and understand that if my suggestions are way off base and/or not possible they wouldn’t waste their time on a wild goose chase.
The PO #1051399.
Charley’s insight on the date being when it was originally opened may be accurate to my issue. 
I don’t know since this was my first time using a PO to send into the Scout store and there were never any listed open ones after I would mark advancements as awarded. I may have inadvertently opened one when learning to navigate SB that stayed opened in the background.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
