Website NOT in sync with MLS

I have gone through our local MLS copy several times to insure that the callings list is correct and current. Most of those changes have populated the website. But there are many duplicates and some of the deleted callings in the local copy do not delete from the website.

Is this a known issue? What can I do to sync the two?

imcurtis wrote:I have gone through our local MLS copy several times to insure that the callings list is correct and current. Most of those changes have populated the website. But there are many duplicates and some of the deleted callings in the local copy do not delete from the website.

Is this a known issue? What can I do to sync the two?

Welcome to the forum imcurtis. I believe there are other instances of deleted MLS callings continuing to show up in lds.org directory listings, and so it is "known issue." Please see the first few posts in THIS THREAD on errors dealing with callings data that persisted across MLS, CDOL (church directory of Leaders) and LDS.org, and how to fix them.

It's a bit dated in its link references, but if I understand it, look at your wards data as showing in CDOL and compare that data to what it should be in your MLS callings. It may be an error in CDOL that needs to be corrected. You can't do it, so send feedback:

For now the best way to get it cleaned up is to send feedback via CDOL of which positions should be deleted.

Does this help?

The good news is that clerks can now fix this for themselves. The steps are:

1. Be on MLS 3.3
2. From MLS do a 'Request Unit Refresh Data...'. (this will include a callings refresh request)
3. After waiting for CDOL to process the request (usually within 15 minutes), do a send/receive to get the refresh.
   1. This will remove all of your callings and replace them with the data from CDOL.
   2. You may want to print out a report like members with callings to refer back to.
4. Cleanup any duplicates and incorrect callings.
   1. MLS 3.3 will now allow you to see duplicates even in the leadership section.

Good luck.

Ah!!
I wondered if that would work but I can't get the dl to work. I went to the www.lds.org and entered my unit number as un and the super secrete password but I can't get logged in. Any ideas?

imcurtis wrote:I went to the www.lds.org and entered my unit number as un and the super secrete password but I can't get logged in. Any ideas?

If you're trying to download mls, use mls.lds.org.

imcurtis wrote:Ah!!
I wondered if that would work but I can't get the dl to work. I went to the www.lds.org and entered my unit number as un and the super secrete password but I can't get logged in. Any ideas?

Full instructions for downloading MLS are on the wiki at MLS download site.

Perfect. Got it now. thanks for all your help

JonesRK wrote:The good news is that clerks can now fix this for themselves. The steps are:

1. Be on MLS 3.3
2. From MLS do a 'Request Unit Refresh Data...'. (this will include a callings refresh request)
3. After waiting for CDOL to process the request (usually within 15 minutes), do a send/receive to get the refresh.
   1. This will remove all of your callings and replace them with the data from CDOL.
   2. You may want to print out a report like members with callings to refer back to.
4. Cleanup any duplicates and incorrect callings.
   1. MLS 3.3 will now allow you to see duplicates even in the leadership section.

Good luck.

I don't know if other clerks have done this, but we had an inconsistency with our MLS and LDS.org directory (CDOL.) We knew we had one calling we changed but CDOL wouldn't update. We did the process above to fix it, and the "unit refresh" brought up two more issues and some blank callings that we had not noticed. All are now correct on both our MLS and lds.org directory (and CDOL.) Thanks MLS 3.3 and CDOL developers! We like problems we can fix ourselves!

I suggest everyone check your MLS callings line-by-line with cdol-

PS: I did a backup first. Make sure you print your MLS callings before your unit refresh, and compare it line-by-line with a second MLS print-out of your callings list after your unit refresh!

kisaac wrote:Thanks MLS 3.3 and CDOL developers!

You're welcome.

kisaac wrote:We like problems we can fix ourselves!

We like problems you can fix too. It's really hard for us to know which bishopric 1st counselor to keep when there are duplicates

I serve in a YSA ward which used to have 2 Elders Quorums; we have since deleted the second quorum, but cannot get 3 callings (and therefore the second quorum) to be removed from online.

I have used the 'Request Unit Refresh Data...' feature several times and did have some callings come through that we did not know we had, but the second Elders Quorum and the 3 phantom callings will not come back. They show up online, but not in our MLS.

Any ideas?

kennethrawlins wrote:I serve in a YSA ward which used to have 2 Elders Quorums; we have since deleted the second quorum, but cannot get 3 callings (and therefore the second quorum) to be removed from online.

I have used the 'Request Unit Refresh Data...' feature several times and did have some callings come through that we did not know we had, but the second Elders Quorum and the 3 phantom callings will not come back. They show up online, but not in our MLS.

Any ideas?

There is a bug in MLS that when you merge to quorums MLS doesn't send up releases for those in the quorum that was merged.

I don't know what you did but it looks like you only have one Elders Quorum presidency now in CDOL. If there are still some there that shouldn't be, let me know and I can clean them up for you.

kennethrawlins wrote:They show up online, but not in our MLS.

Silly question, but where are you checking? If it's the classic LUWS, it doesn't sync with MLS. A website admin has to fix it.

If it's the CDOL or the new directory, it should sync, but it may take a day or two.

Refreshing our unit data worked great and I was able to remove all of the duplicates and old callings from MLS (and now hopefully the website). Unfortunately, now our "Callings by Organization" link pops up "An Error Occurred" instead of the report. The error still occurs after a reboot.

In the log file I found this error:

[E] {Wed 2011-03-02 20:59:55} mls.shell.actions.CmdViewOrganizationDirectories: java.lang.NullPointerException
at mls.organizations.OrganizationDirectoriesTabPanel.init(Unknown Source)
at mls.organizations.OrganizationDirectoriesTabPanel.<init>(Unknown Source)
at mls.shell.actions.CmdViewOrganizationDirectories.doCmd(Unknown Source)
at mls.shell.CMDAction.actionPerformed(Unknown Source)
at org.lds.ics.jtg.tools.widgets.CSLink.fireLinkEvent(Unknown Source)
at org.lds.ics.jtg.tools.widgets.CSLink.mouseReleased(Unknown Source)
at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.1: mls.util.Utils.showGenericErrorPopup(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.2: mls.shell.CMDAction.actionPerformed(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.3: org.lds.ics.jtg.tools.widgets.CSLink.fireLinkEvent(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.4: org.lds.ics.jtg.tools.widgets.CSLink.mouseReleased(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.5: java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.6: java.awt.Component.processMouseEvent(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.7: javax.swing.JComponent.processMouseEvent(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.8: java.awt.Component.processEvent(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.9: java.awt.Container.processEvent(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.10: java.awt.Component.dispatchEventImpl(Unknown Source)

Other units have reported the same issue in the thread "Callings by Organization" is no longer available. Help!. In that same thread post #18 says:

techgy wrote:This problem is being caused by a corruption of the database.
Units that had custom organizational reports had the problem after MLS 3.3 was installed.
The solution is to call MLS Support (801) 240-3500 and advise them.
They will have you do a Send/Receive and then the programmers will send down a script file in a day or so that will correct the problem. Doing another install of the MLS program will not resolve this.

Even though you may be using a later version I think the solution is the same.

This process didn't work at all for me. I requested a Unit Refresh Data. An hour later I did a send/receive, which said that data was refreshed. But nothing has changed. I don't see any duplicate callings in MLS, but there are still plenty on the web site. Any thoughts? Thanks!

mcallaghan wrote:This process didn't work at all for me. I requested a Unit Refresh Data. An hour later I did a send/receive, which said that data was refreshed. But nothing has changed. I don't see any duplicate callings in MLS, but there are still plenty on the web site. Any thoughts? Thanks!

I can see that the request for callings update came in for your Branch and that CDOL sent them back down. Those files aren't waiting so you must have gotten them. There is a large membership file waiting, so I wonder if this process only works correctly if it gets the membership update at the same time (I'm guessing here.) My other thought is if there is something that isn't working correctly for a branch. The other choice is to send feedback within CDOL and let them know which of the duplicates to delete. I am passing this along to the MLS QA staff to see if they know anything else.

My ward has incorrect/old information listed in the new online directory. Would the steps listed in reply #2 solve the problem or are they just for callings? There is a woman with an ex-spouse listed as her head of household, but the information in MLS seems current. Also, I suspect addresses are wrong as some of the automatically placed dots in the new map are at old addresses.

gammaxy wrote: There is a woman with an ex-spouse listed as her head of household, but the information in MLS seems current.

That could be a case of this apparent bug if it involves a non-member spouse. The new online directory does not just report households as defined in MLS, but apparently harvests the name of non-member spouses from the confidential detail within the member's record. So non-member names that do not appear in MLS directories now appear on the website directories. They do not appear on the "classic" website.

That itself would be a serious bug. But the damage can be compounded if a couple is just separated, or if a divorce was never recorded on the member's record. (Such errors of omission are not uncommon, especially among less active members who don't report these facts to ward clerks.) Normally these erroneous details are confined to the confidential membership record and IOS. But because of the website bug, they are being published to the whole stake.

gammaxy wrote:Also, I suspect addresses are wrong as some of the automatically placed dots in the new map are at old addresses.

That is a longstanding issue with the maps website. Apparently the geocoded locations do not get updated in a timely fashion when addresses change.

JonesRK wrote:I can see that the request for callings update came in for your Branch and that CDOL sent them back down. Those files aren't waiting so you must have gotten them. There is a large membership file waiting, so I wonder if this process only works correctly if it gets the membership update at the same time (I'm guessing here.) My other thought is if there is something that isn't working correctly for a branch. The other choice is to send feedback within CDOL and let them know which of the duplicates to delete. I am passing this along to the MLS QA staff to see if they know anything else.

Membership, Finance, Temple or any other files are processed independently of each other. There is no requirement or dependency between receiving or processing files. The data that is contained in the files are written to the MLS database. MLS enforces dependencies of the data once its written to the database.

I have replicated your scenario and do see the duplicates in MLS. I will send you a e-mail of the users I see duplicated so we can compare notes.

We have the issue that is addressed at the biginnning (Callings not in sync). I asked the unit to perform this, but the clerk said that in the past this caused Home teaching , and other things to get dropped... Is this still the case...

Kerryhaxton wrote:We have the issue that is addressed at the biginnning (Callings not in sync). I asked the unit to perform this, but the clerk said that in the past this caused Home teaching , and other things to get dropped... Is this still the case...

That has never been the case. See responses to your similar question in another thread.

I just noticed that we have a number of callings showing in CDOL that have been removed from MLS for, in some cases, more than a month. Will this eventually be corrected or do I need to compile a list and send it to CDOL support?

rpyne wrote:I just noticed that we have a number of callings showing in CDOL that have been removed from MLS for, in some cases, more than a month. Will this eventually be corrected or do I need to compile a list and send it to CDOL support?

Have you worked through the procedure detailed near the beginning of this thread? It seems like that should clean up these inconsistencies, and it's a process you can do yourself.

aebrown wrote:Have you worked through the procedure detailed near the beginning of this thread? It seems like that should clean up these inconsistencies, and it's a process you can do yourself.

So you are telling me to replace my clean data with CHQs bad data and then spend my time cleaning up their mess (again). Last time I did a refresh I was still finding and fixing their mess a month later. I don't think so, CHQ can either keep or fix their own mess. I have enough headache still trying to clean up the mess the CUBS conversion created.

rpyne wrote:So you are telling me to replace my clean data with CHQs bad data and then spend my time cleaning up their mess (again). Last time I did a refresh I was still finding and fixing their mess a month later. I don't think so, CHQ can either keep or fix their own mess. I have enough headache still trying to clean up the mess the CUBS conversion created.

So you are saying that since being on MLS 3.3.x you have done a complete membership refresh, and cleaned up any discrepancies in membership records, addresses, callings, etc. and the changes in MLS didn't make it back to CDOL?

I have the same problem with my ward's website as the original poster. I am willing to try the procedure outlined, but I have some reservations. Will anything else (like home and visiting teaching assignments, HT/VT supervisor assignments, nonmember spouse records, or anything that I haven't considered) potentially be changed by this procedure? I have spent considerable time making sure our records are accurate on MLS; I want to make sure that I don't lose anything.

It seems like a better procedure would be the opposite: wipe out the CDOL data and refresh it from the MLS data, especially in the matter of callings, since all of those are done locally.

esok wrote:I have the same problem with my ward's website as the original poster. I am willing to try the procedure outlined, but I have some reservations. Will anything else (like home and visiting teaching assignments, HT/VT supervisor assignments, nonmember spouse records, or anything that I haven't considered) potentially be changed by this procedure? I have spent considerable time making sure our records are accurate on MLS; I want to make sure that I don't lose anything.

If you follow the procedures found in the section Correcting duplicate or missing callings of the wiki article Callings, only the callings will be affected. All the things you are concerned about being changed will not be affected. The last paragraph of the section mentions a less disruptive procedure for correcting a small number of missing callings.

jbh001 wrote:So you are saying that since being on MLS 3.3.x you have done a complete membership refresh, and cleaned up any discrepancies in membership records, addresses, callings, etc. and the changes in MLS didn't make it back to CDOL?

No, what I am telling you is that BEFORE getting MLS 3.3.x I did a complete membership refresh as instructed by CHQ to supposedly fix some problems and it made such a mess of things that I will never do such a process again.

rpyne wrote:No, what I am telling you is that BEFORE getting MLS 3.3.x I did a complete membership refresh as instructed by CHQ to supposedly fix some problems and it made such a mess of things that I will never do such a process again.

As long as your priesthood leaders support that position, you are welcome to do so. But it seems to me that although keeping your MLS records clean has some value, it has always been more important to make sure that the CHQ records are correct. And that is becoming even more important as website permissions are tied to CHQ records of what callings people have. Suppose, for example, that your own calling were completely correct in MLS, but not on CDOL? You wouldn't even be able to login to CDOL or do a variety of other important tasks.

I know it can be frustrating to have to redo work. But there does seem to be a reasonable hope that the procedure described in the wiki for Correcting duplicate or missing callings will finally get all the callings in sync, so I would be wary of rejecting that option completely based on a bad experience with an earlier version of MLS.

esok wrote:It seems like a better procedure would be the opposite: wipe out the CDOL data and refresh it from the MLS data, especially in the matter of callings, since all of those are done locally.

We discussed that option and for now that option will not be supported. The good news is that eventually the Leader and Clerk application will support editing callings and the changes made their will be directly made within CDOL. That way you will be able to clean up the CDOL data. Any callings that are also in MLS will get updated, but any duplicates/old callings that you are deleting will just go away.

JonesRK wrote:The good news is that clerks can now fix this for themselves. The steps are:

1. Be on MLS 3.3
2. From MLS do a 'Request Unit Refresh Data...'. (this will include a callings refresh request)
3. After waiting for CDOL to process the request (usually within 15 minutes), do a send/receive to get the refresh.
   1. This will remove all of your callings and replace them with the data from CDOL.
   2. You may want to print out a report like members with callings to refer back to.
4. Cleanup any duplicates and incorrect callings.
   1. MLS 3.3 will now allow you to see duplicates even in the leadership section.

Good luck.

I have a follow-up question to these instructions and this post please.

We are seeing a similar thing in our ward unit. The callings in MLS locally are correct and current. However, there are "extra" individuals who are not in our ward unit still showing in callings both on LDS.org and in CDOL. This seems to have occurred in conjunction with a ward boundary realignment which happened recently in our stake. In particular, these are callings across the board in all of our organizations in Primary, Cub Scouts, Sunday School, Young Men, etc. A specific example is we have two sets of individuals now for the Cub Scout Webelos Leaders -- current ward members and the previous members that are not in our unit.

In this case, is doing a "Unit Refresh" the way to correct and fix these callings? Will it properly remove individuals that are no longer in our unit that should no longer have callings in our unit? If not, how do we resolve this?

Thank you.

gsumsion65 wrote:In this case, is doing a "Unit Refresh" the way to correct and fix these callings? Will it properly remove individuals that are no longer in our unit that should no longer have callings in our unit? If not, how do we resolve this?

Doing a "Unit Refresh" will make you MLS copy match what is in CDOL. You will then have to delete the "extra" callings and do a "send/receive" to correct CDOL.

Make sure you print out a copy of all callings before you do the "Unit Refresh" and make sure everything gets fixed in MLS.

rpyne wrote:Doing a "Unit Refresh" will make you MLS copy match what is in CDOL. You will then have to delete the "extra" callings and do a "send/receive" to correct CDOL.

Make sure you print out a copy of all callings before you do the "Unit Refresh" and make sure everything gets fixed in MLS.

The main question is if the member has moved, do they still show up in MLS?

JonesRK wrote:The good news is that clerks can now fix this for themselves. The steps are:

1. Be on MLS 3.3
2. From MLS do a 'Request Unit Refresh Data...'. (this will include a callings refresh request)
3. After waiting for CDOL to process the request (usually within 15 minutes), do a send/receive to get the refresh.
   1. This will remove all of your callings and replace them with the data from CDOL.
   2. You may want to print out a report like members with callings to refer back to.
4. Cleanup any duplicates and incorrect callings.
   1. MLS 3.3 will now allow you to see duplicates even in the leadership section.

Good luck.

Our MLS data is correct but our CDOL data is incorrect will doing a Request Unit Refresh Data replace our correct data with incorrect data

Clay Christianson
Ward Clerk

cchristianson wrote:Our MLS data is correct but our CDOL data is incorrect will doing a Request Unit Refresh Data replace our correct data with incorrect data

Clay Christianson
Ward Clerk

Yes it will. But then you can re-correct MLS and it will update CDOL. If you print out the members with callings report then you will have the information you need to re-correct MLS.