New Member
Person in our ward is shown as in Boy Scout callings as the Assistant Scout Master in lds.org but MLS doesn't show this same calling for the individual. Why the differences between the 2. Is there a different data base? HELP 
There is one master database for storing the official callings for any member, and it is CDOL. The tools on LDS.org take their calling information from CDOL. MLS feeds changes to CDOL, and receives some calling information from CDOL (for example, stake MLS gets its information about ward-level callings from CDOL).pghassing wrote:Person in our ward is shown as in Boy Scout callings as the Assistant Scout Master in lds.org but MLS doesn't show this same calling for the individual. Why the differences between the 2. Is there a different data base?
3 hours should be long enough to get the data back. Unless things are busy, you will have it back in less that 15 minutes. One way to know is to see if the duplicate callings are showing up in MLS. Or you can also watch the send/receive status page (F9). You will see a larger (~10K) CDOL file come down.showseason wrote:Yesterday, my membership clerk tried to clean up some duplicate callings (Primary) on CDOL. Using the info I provided from correct duplicate or missing callings, he did a send for unit refresh data.
He went back to the church almost 3 hours later and did a send/receive again. In the callings listing now (Relief Society specifically) there were no listing for any of the presidency, only other callings. He entered the information for the presidency again and did a send/receive. Now CDOL has duplicate listing for the RS presidency.
He is gun shy now. Do we just need to do the process again? Was the 3 hours long enough to be sure things were done?
The other technique that sometimes helps (but it seems like a long shot in light of the major efforts you've made) is to make a minor change to the calling in MLS (such as changing the set apart flag) and then do a Send/Receive. If that method works, you should see it reflected on CDOL in about 15 minutes.showseason wrote:I must be doing something wrong. I sent the refresh data request yesterday morning some 23 hours ago. Back today and did send/receive, getting message it had been refreshed (created). The MLS calling data appears the same, and does not reflect CDOL information, which had the duplicate listings. Is there something else to try?
That may be. I do see that all the ward's other callings are now listed under Primary heading - sent feedback on that.RussellHltn wrote:There was a recent upgrade to CDOL. I'm wondering if it added some new bugs.
I looked at what we were sending down and for some reason it was only sending down refresh data for the stake callings, even though the refresh request included both the ward and the stake. I took the liberty to trigger the refresh from CDOL (which might be the way it was tested the most), and I see that the data that is ready to come down has the right number of callings for your stake and ward. I hope that helps.showseason wrote:Back again. The supposed refresh came back, but MLS still does not mirror CDOL. Those calls I deleted in MLS helped CDOL and that's a big fix, but now MLS shows holes. I could add the callings back and not do a send/receive but that seems like just postponing the inevidable. Looks like time to make a call to SL.
It looks like the refresh has a bug in it somewhere. We'll have to look into it.RussellHltn wrote:There was a recent upgrade to CDOL. I'm wondering if it added some new bugs.
JonesRK wrote:I took the liberty to trigger the refresh from CDOL
I've been watching this thread, and checking to see what was going onRussellHltn wrote:I was hoping to attract the attention of our friendly neighborhood CDOL developer.![]()
Unfortunately, no. We have talked about that possibility, but it hasn't ever happened. I'll bring it up again.RussellHltn wrote:Is that something that someone in the local unit can do?
JonesRK wrote:I took the liberty to trigger the refresh from CDOL (which might be the way it was tested the most), and I see that the data that is ready to come down has the right number of callings for your stake and ward. I hope that helps.
Okay, I marked your unit to request a backup so I can see if I can figure out what is happening. So the next time you do a send/receive, I'll get that and see if I can figure out what isn't working.showseason wrote:Early this morning I signed on and did and send/receive. Different messages came up and something about callings (so fast I did not catch it all). I was hoping it was fixed. But . . MLS did not pick up the CDOL list.
JonesRK wrote:Okay, I marked your unit to request a backup so I can see if I can figure out what is happening. So the next time you do a send/receive, I'll get that and see if I can figure out what isn't working.
The bug applies to refresh requests initiated by MLS. In your case there was a problem with MLS processing the full refresh file that I generated from CDOL. We gave that to the MLS team to look at. I haven't heard anything back. I will follow up on Monday. If you want to PM me a list of the duplicates I can delete them from CDOL.showseason wrote:My Bishop is asking if it is just our ward or a church wide issue that prevents us from receiving a unit refresh data back to correct our MLS calling list (Salt Lake is aware). I could not answer him so would like to know if others are having an issue too. We will have a organization change tomorrow and if I enter it in MLS it will duplicate in CDOL with different peoples names since the current calling is no longer in MLS to change/remove.
Update found on other thread: We just found a bug with CDOL processing the refresh request coming from MLS 3.4.3. Note: this bug will be fixed in the CDOL 3.1.1 release (hopefully next week).
This was concerning a stake problem - Does it also apply to a ward issue?