callings shown on lds.org don't match MLS

[jefftenney]

We have several callings showing up on lds.org for people who have been released for several weeks. Most of our callings changes show up on lds.org within hours.

My best theory is that these "old callings" appear any time I remove both the person and the calling/position in MLS. But I'm still testing that theory.

How can I clean house in lds.org so the callings will match MLS exactly?

Jeff

[russellhltn]

See Correcting duplicate or missing callings.

[jefftenney]

Thanks.

I'll give it a try. Although it does seem backwards. The data in MLS is already correct, and the data in CDOL is wrong. I wish I could tell CDOL to purge everything and just start fresh with the MLS data. Sadly, the suggested action is to purge MLS, get the CDOL data into MLS, correct the data in MLS, and then send/receive.

The last step is ironic because we end up counting on CDOL to recognize all of the changes, which it has already proven it cannot do reliably.

I'm still willing to try it, but does anybody know of another way?

Jeff

[aebrown]

The last step is ironic because we end up counting on CDOL to recognize all of the changes, which it has already proven it cannot do reliably.

I'm still willing to try it, but does anybody know of another way?

The only way you have to change callings is through MLS. So this recommended process may seem backwards, but it actually makes a lot of sense. You first make sure that MLS matches the master list (CDOL) and then you make changes in the only place you have control over (MLS), which insures that those changes will be transmitted to CDOL, and thus CDOL will match MLS.

Sure, we could all think of alternate techniques that affect CDOL directly, but they don't exist -- or at least they don't exist at the ward/stake level. So given the tools that we have, this is the best approach. And please note that many of these problems with being out of sync are longstanding problems. The approach for correcting duplicate and missing callings gives you a fresh start, and moving forward the synchronization is much more reliable. When I first worked through this process over a year ago, we had several callings out of sync. Since then, not a single calling has been out of sync.

I'd recommend that you work through the process so that you have a solid starting point, and then see if you still want to claim that CDOL can't handle subsequent changes reliably.

[jefftenney]

Thanks for the explanation. You're right, it does make sense. And as you say, once the two are properly in sync maybe CDOL will keep up better.

Thanks again for the advice and for being so fast with the information I needed. Great stuff. Very helpful.

[jefftenney]

As a follow up, this process did seem to help a lot. It was somewhat painful having to start with the CDOL copy of the callings and then add/remove callings to get back to where MLS already was. However, since then, CDOL has indeed kept up with the changes I've been making in MLS. I can't say the callings in CDOL match perfectly now, but the remaining errors seem inconsequential. So thanks for the good advice.

[jdlessley]

I can't say the callings in CDOL match perfectly now, but the remaining errors seem inconsequential.

There was an update to CDOL that was made after the August 17th postings. In order for the Correcting duplicate or missing callings procedure to work units need to have MLS 3.5 installed. MLS 3.5 has not yet been released. Until it is, the recommendation is to do nothing. Following the procedures in the Correcting duplicate or missing callings procedure may only make things worse.

[jefftenney]

Wow, then I am really glad I followed the procedure before the recent CDOL update. Any hint as to the release timing for MLS 3.5?

[jdlessley]

Any hint as to the release timing for MLS 3.5?

It is beta testing right now. Any further schedule has not been released.