All of the Lions and Tigers have multiple profiles attached to the youth but they are all the same profile (ID, content, etc. is all the same). This is happening on both parents and leaders.
Mine so I know there are no duplicate profiles.
All of the Lions and Tigers have multiple profiles attached to the youth but they are all the same profile (ID, content, etc. is all the same). This is happening on both parents and leaders.
Mine so I know there are no duplicate profiles.
If it is the same MID and SB User ID of the Parent - then it is the Council adding relationships of different kinds - ex. Scout of XXXX, Lion of XXX, Tiger of XXX
I guess you are seeing this in SB+?
So in 6 years, I can expect 7 “Scout or Rank of” parent profiles under each Scout?
Yes, SB+
No it is just old relationships - I did bring it up to Developers. Not every rank has relationships.
Lion and Tiger adult partners are a special relationship that is added in addition to the parent relationships, as that person needs to be identified.
I can understand that but 1 of those entries cover last year. The scouts are Tigers now (and a week away from Wolf). So at least a third of the information provided is inaccurate and irrelevant. They are no longer the “Lion of”.
It looks like the council has all of those relationships active, whereas only two (Tiger of…/Son of… or Lion of…/Son of…) would be active for the scouts at a time. It also looks like the calendar module is identifying all of the “active” roles and serving an RSVP slot for each role. To me, it seems like the coding logic for the calendar should be selecting “Parent of…” over “Lion/Tiger of…” where both exist (e.g. parents who are both parent and Adult Partner), but that might not be the intended function. Hard to say without knowing how it’s coded, but maybe worth bringing up with devs to raise with policy folks for clarification? Nevermind. Donovan already said he raised it. Gotta work on that reading thing…
There is no Current status for these types of relationships - it is Null or True
Ah. So the status has to be “revoked” when it expires, if that’s even the right way to think of it, or it continues to appear. Interesting way to code a relationship that only exists temporarily. Probably wasn’t an issue before the greater integration of the systems.
Thanks for the insight!
I have the the same entries you do for my now 14-yr old. It’s just how it is in the database. Now whether they all need to be displayed is a question we are discussing with the developers.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.