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.
I am a Council Admin for MBC in Council 421 - I have a MBC, MID 137528536 - We just onboarded this volunteer as a new first time merit badge counselor a few days ago. In AKELA, his contact phone number has the correct area code of “828”. However, when we look him up in Scoutbook Legacy under the MBC list, his phone area code is listed as “282”. I have verified with him, and on his adult application that the correct area code is “828”. See the screen shot I attached.
Based on the search results, there is no active 3-digit North American Numbering Plan (NANP) area code “282” currently assigned to a specific geographic region.
My point is that there has somehow been a transposition mistake, but we cannot figure out how to resolve it.
The MBC should log in to either Scoutbook Plus or my.scouting.org and update their phone number. If it is correct when the view it, change it to an invalid number, save then change back. This will ensure all systems are in sync.
Update; They never saw it as wrong in their MYST of Scoutbook profile. They changed it to something invalid, then changed it the corr ect number. After last night’s sync, it is showing correct now. SUAC should discuss this with AKELA folks and have the phone number to be one of the fields that can be synced in mybsa2 - just a thought. Thanks for the hack.
We have had multiple discussions and the issue with syncing data from one platform to another without the use making a change is that we do not know which is correct. Prior to Akela and Scoutbook syncing automatically, there were and still remain some cases where Akela hold the correct data and others where Scoutbook holds the correct data.
