Hi, I have 8 adults with multiple IDs. I’m not sure why, but it is a real pain when documenting activities in the activity log. Is it possible to merge them?
I have done these first 4. I will provide more details tomorrow.
Hi Jennifer,
Thanks so much. I suspect this is happening because:
I’m not sure what is the best way to avoid this so I am open to suggestions.
When registering for new positions, using the existing my.scouting.org ID will help ensure a new Member ID is not generated. If using a paper app, writing the current Member ID on the app tells the registrar to use that current MID. Also, always using full legal name helps the system match existing accounts.
Changing Councils will always generate a new MID as each Council has their own.
And using the same full name, is often an issue to make a second number
This one is fixed. I recommend that this user log in to her my.Scouting account and double-check her e-mail there, because there were 2 different e-mails for her.
This one is fixed. Please have this user contact the local council and ask them to use their Registrar Tools to look up his child (or children). In the “Relationships” tab / section, he should only be listed as parent under his primary member ID number: 133317513. He should be removed as parent under any other member ID numbers to help prevent the creation of duplicate Scoutbook accounts.
In this case, the user had an existing member ID number, but created a second one when he created an account at my.Scouting using a nickname, so the system did not find a match.
This one is fixed. Please have this user contact the local council and ask them to use their Registrar Tools to look up his child (or children). In the “Relationships” tab / section, he should only be listed as parent under his primary member ID number: 12880746. He should be removed as parent under any other member ID numbers to help prevent the creation of duplicate Scoutbook accounts.
Like 6 (above), the user had an existing member ID number, but created a second one when he created an account at my.Scouting using a nickname, so the system did not find a match.
This is fixed. Please have this user contact the local council and ask them to use their Registrar Tools to look up his child (or children). In the “Relationships” tab / section, he should only be listed as parent under his primary member ID number: 141287919.
Like 6 (above), the user had an existing member ID number, but created a second one when he created an account at my.Scouting using a nickname, so the system did not find a match.
Member ID (MID) 14736122 was created with a blank date of birth, which usually indicates that the unit most likely created it as part of Scoutbook’s invitation process.
My recommendation is to ask parents to create an account for themselves at my.Scouting using their full name (not a nickname). Then they can log in to Scoutbook (legacy) with the same my.Scouting username and password (single sign on).
Two of these MIDs have a blank DOB, so they were most likely created by the unit using Scoutbook’s invitation process.
Same issue here. One MID has a blank DOB, so was most likely created by the unit.
This one is fixed. Please have this user contact the local council and ask them to use their Registrar Tools to look up his child (or children). In the “Relationships” tab / section, he should only be listed as parent under his primary member ID number: 13321971. He should be removed as parent under any other member ID numbers to help prevent the creation of duplicate Scoutbook accounts.
Thanks for your help. I contacted someone at the council membership & unit services team who is going to connect me with the right person. Thanks again!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
© 2019 Boy Scouts of America - All Rights Reserved
