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.
This is an extraordinary thread, revealing a systemic problem affecting some percentage of individual membership renewals nationwide. Spot checking four unit roster CSV exports in my district, I found four missing P_G relationships.
Is there a way for council registrars to proactively identify these missing parent child relationships council-wide and notify unit leaders?
Or is the only way to find these to export roster CSV files at the unit level?
This is an important issue that all unit key 3 and commissioners could be advised to check for over the next couple of months as they work through recharter.
@PaulStrasma - in reality it should have always been a part of recharter to do a unit membership true up on emails, addresses, parent relationships. Our council sent out an email requesting that we do that as part of the process.
@Stephen_Hornak thanks for sending your council’s communication. I note the section highlighting that “all member email addresses need to be correct/current in MyScouting or Scoutbook Plus”.
What’s extraordinary here is that the P_G_Email address field used for membership notifications is only accessible from a myScouting roster CSV report export. The relationships visible to unit leaders in Scoutbook Plus (and legacy Scoutbook) aren’t necessarily the same.
For a specific example, check out member ID 130983606. This one has a blank in the P_G_Email address field but shows a parent/guardian relationship in Scoutbook Plus. Clicking through to that parent in Scoutbook Plus generates an error “Person not found for given person GUID - personGuid: 37E6ACBB-407F-4556-A104-DA060FC9F979”. Looking up that parent in legacy Scoutbook, everything looks just fine with a proper e-mail and contact.
I recognize the answer to these issues is “contact your registrar”. I’m just trying to figure out how we could be proactive rather than reactive to this issue.
