Website NOT in sync with MLS

[gsumsion65]

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.

[rpyne]

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.

[jonesrk]

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?

[CChristianson]

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

[jonesrk]

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.