What is all this Relationship stuff and where are my Scoutbook Parents?

OK to try to clear this up.

Legacy Scoutbook had CONNECTIONS - those were user made to connect an adult to a Scout - leaders or Parents could make connections. Connections attached on SB USER (not name) to another, some people have multiple SB USERS all with no Member ID (MID) or different MIDs.

RELATIONSHIPS are what is used in other Scouting Platforms and so many exist. It is RELATIONSHIPS (of a certain order, ex Parent) that allow a user to Register or renew a registration for a Scout. Traditionally these were made through the application process, or only a Council could add them to a scout. Now that has been extended to users, and the parents in RELATIONSHIP get an email, to validate and confirm the Relationship. RELATIONSHIPS reside on the MID (not name) - and as we know many people have several MIDs they know of, and even MIDs they are not aware of having.

Here you see Scout Trenton. On the Left you see mother Andrea is listed under SB+ Relationships. That means, she is the only parent listed in that database for this scout, otherwise others would appear.

If we look at the Legacy CONNECTIONS we see a few things. We see mother Andrea never finished the SB Connection and there are 2 for her which means 2 different User accounts for her. Father Eric did complete the SB Connection but that is not a RELATIONSHIP, so when he logs in he will get the Warning you need a Relationship.

On the SB+ you will see Andrea shows her MID - that is a feature coming soon to help users and units identify if the log in being used is the parent Relationship needed or is it a secondary MID that you might need council help with.

On SB+ you might see a parent listed multiple times under relationships, that is because that parent is listed under the Scout with Multiple MIDs from the same council or from several councils do to moves.

–––––––––––––––––––––––––––––––––––––––––––––––––––––

ADDING RELATIONSHIPS:

A Parent currently IN a RELATIONSHIP and signed in under that MID - can go to a Scouts SB+ Profile > Click the + under the Relationship area > Search for other parents that need to be added. This starts a process of emails and logins to establish the Relationship (it is already Validated as a Parent started the Process.) DO PAY ATTENTION: the list of relationship types is long - read the relationship and make sure it is correct kind of relationship - currently only Parents will show for unit and unit events. There is a guardian FLAG council can set that makes others show in SB+, this is different from the Guardian relationship you might see as option.

MOST users that have a SB User also have an MID, if they know it or not, it can be seen on their SB User profile.

A Unit Leader can do the same, but a Parent in Relationship is first notified with email and must take action to Validate the choice.

Current Registered Leaders that can make relationships

Chartered Organization Rep.
Committee Chair
Council Unit Representative
Cubmaster
Scoutmaster
Venturing Crew Advisor
Skipper
Exploring Post Advisor
COR/CUR Delegate
Key 3 Delegate
Scoutbook Admin

Councils can also add relationships when needed.

When adding a relationship - you want to confirm that the Parent can log into the account using that MID - just the same name is not enough.

1 Like

I need help with this. I have a parent who shows connected in legacy scoutbook but not in scoutbook plus. I (CC) tried to add her as a parent in scoutbook plus, using her member ID. It says pending on my end and sent her an email. When she clicks on the email, it tells her she doesn’t have access to scoutbook plus and routes to legacy scoutbook or my.scouting. Legacy scoutbook also now gives her a warning that another user is using the same email address.

@AshleyBridwell Please post the parent’s member ID number.

(No names, please)

Member ID is 141668234

@AshleyBridwell That user had a duplicate Scoutbook account. They have been mereged.

Thank you. Should they be able to log in to scoutbook plus with the correct permissions now?

@AshleyBridwell Ask the user to log all the way out, then log back in again.

I am having an issue trying to add relationships to one of our Scouts. I can click add relationship for the scout, and can search and find the mother with scouting id and birthdate. Once I try to save that relationship, I keep getting an error saying subUnitId and subUnitType are required. But they are not being passed on the call to create the relationship. See attached images.

API Request URL:


Payload being sent (I removed some values). Notice nothing about subUnits in the payload.

Response with error.

Scouts MID in this case is 133443676
Thank you for any assistance,

Greg

@GregKing - this is Mother 12487086? She has 2 positions in Troop 34 - USR and ASM - that should not be possible. Wondering if that is gumming things up?

@DonovanMcNeil Thanks for the quick response. Yes, Mother is MID: 12487086. I used the mother because I thought that was going to be the easy one :). Father is connected to son in Scoutbook Plus showing with MID: 133443677. However, the account he sent me to try to connect was MID: 134620346. If I try to connect 134620346, I get the same subUnit error.

-Greg

@GregKing hmmmmm - in SB+ - make a patrol and put that scout in it - see if that solves it - would answer the sub-unit you saw

Dad has relationships to 2 scouts under 133443677 - but is registered under the other - that is a tell council and let them clean up I think

He was in a patrol originally when I started. I removed him from the patrol (and accidentally deleted the entire patrol in SB+) to see if that was the issue. I can try to create a new patrol and put him in it and see. Will let you know. Will get the father to clear that up with our council. Thanks.

Yes do try a new patrol - that would help define the Bug

I tried adding the Scout to a patrol. I got an error due to his Den Chief position and an invalid packId. I tried to end that position in SB+ by putting an end date, but got an error saying there must be an active Den Chief position. I went back into legacy ScoutBook and put an end date in for DenChief and it now showed as a past position in SB and SB+. I was able to add the Scout to one of our existing patrols. Tried to add a relationship, same error. I added the parent to that same patrol, still invalid subUnitId and subUnitType. I then removed both Scout and parent, created a new patrol and added the Scout to it. Still the same error. Those two values are never passed on the request payload, it’s only the values I posted above. I have to step out, but let me know if you have anything else you would like me to try/test. Thanks, Greg

It looks specific to this Scout in our troop. I was able to initiate a parent relationship to my spouse for my own Scout successfully as she was only connected in legacy Scoutbook. I also looked at the request payload to the api for that successful call, and it did not include subUnitType or subUnitId. So that must be something happening behind the api call related to this Scout.

Thank you for attempting to bring clarity to this extraordinarily complicated database merger fiasco.

I think I found a good test case. Troop move between cub and bsa, Mom and Dad are heroes and support both old troop and new troop in various positions, etc. I’ll keep trying things, but let me know if a fix is coming or you find a workaround. We’ve got a little time, it’s only trying to get the relationships corrected.

@GregKing the true easiest way is for Council to do it - as they should have had the relationships in place. Main key is to make sure users can log into the MID that is used for the relationship.

@DonovanMcNeil Thanks, I’ll send them that way.