Primary Class Merge

Discussions around using and interfacing with the Church MLS program.
Posts: 108
Joined: Thu Oct 27, 2011 8:22 pm

Primary Class Merge

Postby chris_hazeldine » Tue Jan 22, 2013 9:50 am

Apologies if this has been address elsewhere - I tried searching the posts but couldn't find anything on the topic.

For the 2013 Primary Classes we have been working through the Stake assisting the Ward Clerks to represent the actual classes in the units in MLS. This has meant a number of classes being merged and split depending on what is happening in the unit.

What I have observed has been interesting, and seems to be a pretty major bug but appreciate it if someone could provide any feedback or replicate and see if it can be corrected.

After merging the Valiant 10 and 11 for example, once MLS got back confirmation of change of records and a batch of Member Record Prints on Send/Receive, half of the class was now no longer linked to the class. In the record there were no organisations/classes listed and they no longer appeared on the rolls. We took Valiant 11 and merged with Valiant 10 and it seems that the Valiant 11 class members were the ones that are no longer linked to the class. This occurred for CTR classes also.

Anything that anyone has seen before? It occurred on all units where we had a class that needed to be merged.

Chris Hazeldine
Stake Executive Secretary

New Member
Posts: 13
Joined: Tue Oct 26, 2010 8:54 pm
Location: USA

Re: Primary Class Merge

Postby brogers » Tue Jan 22, 2013 11:28 am

I think we had the same thing happen to us as well.

Community Moderators
Posts: 6503
Joined: Sun Mar 16, 2008 11:30 pm
Location: USA, TX

Re: Primary Class Merge

Postby jdlessley » Tue Jan 22, 2013 1:52 pm

It sounds like when the two classes are merged the membership rules for one of the merged classes becomes the membership rules for the new merged class. Since the members of one of the merged classes do not meet the membership rules of the newly merged class then they are orphaned.

When merging Valiant 11 with Valiant 10 I am guessing the "merge" link was clicked for the Valiant 11 class. This would mean the Valiant 11 class was merged into the Valiant 10 class and then named something like "Valiant 10 & 11" in the "Merge Class" dialogue box. If my theory about class rules is correct then the Valiant 10 & 11 class would inherit the class rules for the former Valiant 10 class.

I did not complete the full process of merging classes and doing a send/receive because I did not want to unnecessarily mess up our Primary classes. But I did merge the Valiant 11 class with the Valiant 10 class temporarily. Normally the rules for a class can be viewed by clicking the name of the class. That opens the edit class dialogue that displays the class rules. In the case of the merged class I noted the class rule for "Minimum Age at Beginning of Year" was blank. I have no idea whether or not this has any bearing on the bug discussed in this thread.
JD Lessley
Have you tried finding your answer on the Help Center page or the LDSTech wiki?

Community Administrator
Posts: 20517
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Re: Primary Class Merge

Postby russellhltn » Tue Jan 22, 2013 2:17 pm

What would happen if you merge the Valiant 10 with Valiant 11? I think Alan had noted that it was easier to merge the younger YW with the older group then the other way around.
Have you searched the Wiki?
Try using a Google search by adding "" to the search criteria.

Return to “MLS Support, Help, and Feedback”

Who is online

Users browsing this forum: No registered users and 1 guest