Ward leaders

Hello,
All our YM and RS leaders are placed correctly in MLS but in lds.org directory they show up in Young Men (president and one councelor) and Young Men presidency (one councelor). Why do they show up i different groups? The same for the Relief Society precidency.
Regards
Christian

As long as your ward clerk gave these people the correct calling (i.e., he choose one from the list and didn't type it in) in MLS this should show up in the same group in Directory. Please check with your ward clerk to see if everything's correct. Thanks.

Verify that the calling is recorded as a standard position and not a custom position.

The recent MLS 3.5 upgrade may have caused some problems. I didn't do the upgrade in our ward, but I understand there were problems with some callings getting messed up that had to be cleaned up after the upgrade. Check with your ward clerk. Make sure he's aware of the issue. Hopefully it's a quick fix.

I'm sure you meant to write MLS 3.5 rather than 4.5, correct?

We're beta testing 4.5 in our ward

Looks like you caught a typo in my post. I'll go fix it.

Yes, the positions are standard positions and yes it appeared after the latest upgrade to 3.5

The problem is a data inconsistency in CDOL caused by CDOL supporting the new 3.5 data structure, but MLS still being on 3.4.3 . We have a script that cleans this up. It should be in production today or tomorrow. Then I can run it for your ward and make sure that it fixes things on lds.org directory

I have run this and from what I can see it looks good. Let me know if you see anything.

I am having the same problem for our ward, after upgrading to 3.5 any changes made in MLS to ward leadership positions are not being updated on the lds.org website.

tetonedge wrote:I am having the same problem for our ward...

If your issue is truly the same as reported by the OP in this thread then you should find the callings in the LDS.org Directory. They just may not be where you would expect to find them. But if those new callings do not show in the Directory at all after doing a send/receive and waiting a few minutes then you have a different issue.

How long has it been since you made the changes in MLS and did a send/receive? Have you checked CDOL to see if they are listed there? If they are not in CDOL, then try another send/receive. After waiting some time and the changes do not appear in CDOL then make a change, such as the set apart flag, save, set it back to what it was, and do another send/receive.

I have triple checked both CDOL and MLS (3.5) to ensure the callings are correctly entered. How ever on the directory in lds.org, ALL the primary classes so up under the leadership section

Graham1 wrote:I have triple checked both CDOL and MLS (3.5) to ensure the callings are correctly entered. How ever on the directory in lds.org, ALL the primary classes so up under the leadership section

That will be fixed today or tomorrow. We are currently running a clean up job in the database for each unit. When it gets to your unit it will fix this.

The clean up job should get things back in sync better now that most people are on MLS 3.5. The things it is doing are:
1) Moving positions to the correct organization (e.g. Elders Quorum President to the Elders Quorum Presidency)
2) Moving and organizations to their correct parent/child location (e.g. Primary classes under the Primary)
3) Remove any duplicate organizations that aren't allowed more than one (e.g. remove a second Bishopric)
4) Fix the top level organization information stored with the position (this cleans up how they show in the directory)

The hope is that with this cleanup and MLS 3.5.1 refreshing its positions from CDOL things will be in sync and start working more smoothly.

I am the Stake Clerk. Some of our wards have mentioned a problem with a calling having a double entry. One of our ward relief society has this problem now. I have been on the ward callings list and tried to remove the double entries. Yes, they are in a Stared calling position. I deleted all of the ward relief society. It did not remove the callings from LDS.org. MLS showed no positions in the ward Relief society after send and receive. LDS.org after a time period showed the president listed 1x, first counselor listed 2x, and second counselor listed 1x. The next day I added the relief society presidency back in MLS, did a send/receive. Now MLS is correct, but now LDS.org shows; President listed 2x, 1st Counselor listed 3x, and 2nd Counselor listed 2x. Also, I see today LDS.org has an additional sister entered as a second Counselor which is in error also. How do we get these callings off of LDS.org and callings to match MLS?

woody55 wrote:How do we get these callings off of LDS.org and callings to match MLS?

First, make sure your units are on MLS 3.5. Then follow the instructions for Correcting duplicate or missing callings.

aebrown wrote:First, make sure your units are on MLS 3.5. Then follow the instructions for Correcting duplicate or missing callings.

Due to a bug in MLS 3.5 not showing all the duplicates, you might have to remove the presidency in MLS, do the send/receive, request a unit data refresh. After that comes down you should be able to see some more of the duplicates. Repeat this until all the incorrect callings are gone. Then you can put back in the correct ones.

JonesRK wrote:Due to a bug in MLS 3.5 not showing all the duplicates

Is a fix for this bug in the pipeline?

I've seen mention of 3.5.1, but don't know the rollout status.

RussellHltn wrote:I've seen mention of 3.5.1, but don't know the rollout status.

The MLS Release Notification page says it will be out in December and is currently being beta tested. Of course, it doesn't say if this particular bug is in there but I would think it would be.

eblood66 wrote:Of course, it doesn't say if this particular bug is in there but I would think it would be.

I would hope that the bug is not in there, but that the fix is.

aebrown wrote:I would hope that the bug is not in there, but that the fix is.

Right you are!

eblood66 wrote:The MLS Release Notification page says it will be out in December and is currently being beta tested. Of course, it doesn't say if this particular bug is in there but I would think it would be.

The fix is not in 3.5.1. We discussed it in a meeting today with MLS and they are trying to reproduce it today. It would be useful to know if the steps I outlined in post #16 work to fix it. If so we can update the wiki with a work around for now.