Welcome! This forum has a treasure trove of great info â Scouters helping Scouters! Just a heads up, though - all content, information, and opinions shared on this forum are those of the author, not the BSA.
In addition to @DonovanMcNeilâs suggestion, there might be be another place to look. Based on some reports that future events created in the Activity Logs are propagating into the Scoutbook calendar, I would look there if the Audit Logs donât get you enough information. If thatâs whatâs wrong, why itâs happening isnât as clear, at least not publicly. Current speculation is a feature under development that made it from the testing system into production.
Working around the issue (if this is the actual cause) consists of removing the âfutureâ events from the Activity Logs.
Another possible cause might be that the event is listed on multiple unit calendars, and only someone who has edit access to all of those calendars can edit the event.
Note: the locations for all of these mystery events are places in San Jose, CA where our troop is located. Are these coming from sort of council or district calendar?
Looking at the audit logs, were you able to identify who is creating the events @JoeMcKinley? If so, and they arenât supposed to be doing so based on unit policy/practice, you probably want to coordinate with them about getting activities entered through the unitâs preferred pathway.
That said, it does seem like this is an under-development feature thatâs leaked to the production server. There hasnât been (as far as Iâve seen in the change logs) an announced new feature to have events entered in the activity logs add themselves to the Scoutbook calendar. Assuming that the events arenât being added via some other pathway (e.g. added to multiple unit calendars), could someone ping development about the feature-leak possibility, @DonovanMcNeil?
So, I tried creating an event in the service logs, then editing the number of participants, and was able to reproduce the behavior youâre seeing, @JoeMcKinley. Similarly, the Audit Logs were silent about the creation of the event in the service log, the creation of the calendar event, or their subsequent deletion. At the very least, the logs should be capturing these events.
It definitely looks like a development feature leak.
@CharleyHamilton - I was going to note that this seems like the calendar module that had hit and then was backed out. The tough part of all of this is the ASP that has its reach in scoutbook and the attempt to merge into the IA stack.
Yeah, hopefully development is able to identify whatâs going on (the issue raised by @JoeMcKinley), and the separate issue of why itâs circumventing the logs. It seems like even automated processes should be hitting the logs to indicate that a change was made, when, and by whom (i.e. the username accessing IA2), although even noting a reason of âsynchronization with IA2 activity logsâ would be an improvement over silence.
Itâs not a user entry, itâs a systemic issue as I am seeing this too. It pulls forward into Google & iPhone calendar syncs too. It is causing confusion & frustration among my new parents when they see lackluster detail & follow a dead link.
I am the only admin entering unit events in the calendar & group activities in the logs (and the only one who knows the ___ BBcode that calendar still requires to make a hyperlink).
I had an existing calendar event, and an existing group Hiking Activity entry, the time came & went. A few days past, I updated the Attendance in the calendar event & added participants to the Activity Log. Thatâs when this fake calendar event showed up.
Looking back now at the Activity Log entry it shows a flyout âThis activity is associated with a calendar eventâ even though there is no means to link them from the Edit screen. I assume it refers to the fake event. Normally Activity Log entries just show âThis is a group activityâ.
Combing back a few months I can see a few other times that random activities show the âassociated with a calendar eventâ message, & sure enough only those have duplicated fake events on our calendar.
I did not know about the Audit Log previously, thanks for that tip! But I must say, they are not too helpful or reliable at the moment. These entries show the start date & time of the Activity Log event in question. But the 7 Scouts listed here were not added to the Activity Log entry until a week later (there was no Audit Log entry for that action). User is âUnknownâ, so based on the times I had assumed this was some automated action by ScoutBook flipping it to a past event, yet I was the one to add those exact scouts days later so the entries just donât make sense ( I also added adults, which donât appear in the Audit log).
This series of entries shows me adding a new future event, & then updating the attendance of a past existing event, yet user is âUnknownâ for both. While another action I did in the middle has my name correctly. Other times in the Audit logs it shows me as âJoshua J Joshuaâ, which is just odd.
I am happy to see that there is an effort underway to sync the Activity Logs & Calendar, which is long overdue, having to always enter everything twice has been a pain. However, this is not ready for prime time. I also think it should be done the other way around: the Calendar is our main source, then we should have the ability to tag or pull data from that event when adding/editing an Activity entry.