LDS tools not syncing callings

Provo YSA ward (163rd) cannot get LDS tools to sync calling data with MLS. Directory data seems to work without problem. An attempt was made to sync our local MLS with headquarters but just deleted everything entered in MLS and nothing was fixed. Can someone look into this further for us?

CDOL is the center of this. MLS syncs with CDOL and LDS Tools gets it's information from CDOL.

Most likely the issue is the MLS to CDOL sync. Try following the procedure in Correcting duplicate or missing callings. Also be aware of Difference between standard positions and custom positions. Always use standard positions when possible. Things may not work properly for custom positions.

Lastly, since you are a YSA ward, make sure you've properly created the Out of Unit Record for your leaders. Failure to fill in all the fields could cause problems for those callings.

Last note:

ercorbett wrote:Can someone look into this further for us?

This is primarily a user-to-user support site. A few church employees visit to help out from time to time, but they mostly deal with bugs in the system. One-on-one help from people who can actually access your data comes from making a call to Local Unit Support. But I would go over the links I posted above, first.

I am seeing a similar issue with just a few specific callings.

for example, Our YW presidency is listed in MLS properly.
I logged into CDOL and verified they are listed there as well, just as they should be.
However, in LDS Tools all members of the YW presidency are NOT listed as having a calling.
In fact they are all on the "members without callings" report in LDS Tools. very odd.

The steps to sync MLS with CDOL is not really the case that I can see, CDOL does have the callings listed correctly and it appears CDOL is not getting Sync'd with LDS Tools.

To trouble shoot I have even tried removing all cached data for LDS Tools, uninstalling it. And re-installing and re-syncing fresh.. the issue still exists.

I am using LDS Tools on Android 4.4.4, and am unsure if this specific issue exists for IOS.

I am curious of other users may have seen similar? and if they have found a resolution.

jbarchibald wrote:However, in LDS Tools all members of the YW presidency are NOT listed as having a calling.

Are you referring to a report of members without callings, or are you looking at the individual and not seeing a calling?

jbarchibald wrote:I am using LDS Tools on Android 4.4.4, and am unsure if this specific issue exists for IOS.

Is there an Apple user in your ward you can check with? It would be nice to know if this is a Android issue for a API Service issue. It makes a difference what team is involved.

Are you referring to a report of members without callings, or are you looking at the individual and not seeing a calling?

Both, if I look at the report, they are on the members without callings as if they have no calling, and if I look at the individual record there is no Calling listed for those specific sisters.

it is odd in that it is the entire YW presidency. I have also validated that we are using Standard callings in MLS, and not custom ones.

Is there an Apple user in your ward you can check with? It would be nice to know if this is a Android issue for a API Service issue. It makes a difference what team is involved.

Yes,, I think a few of them do, I have sent a request to them, and when I hear back I will post the results of their findings.

Is there an Apple user in your ward you can check with? It would be nice to know if this is a Android issue for a API Service issue. It makes a difference what team is involved.

UPDATE:

have a response from others in my ward that are using the iPhone version of LDS Tools.
they have the same situation where certain members have valid callings listed in MLS and CDOL, but they do not appear in LDS Tools.

It appears to NOT just be an android issue.

It turns out our ward is having the exact same issue with the YW presidency not showing up. Everything is correct in MLS and CDOL. It's a problem with both iOS and Android. All other callings are fine. Not sure what to do next. Thoughts?

Also, nothing has changed in the presidency and everything used to show up a month or two ago (not sure on exact timeline)

I can verify this is a problem. I added two callings in MLS this afternoon. They appeared in the online Directory within minutes after the MLS send/receive. They also appear in CDOL. I have synced LDS Tools three times since they appeared in the online Directory. The latest sync was three hours after the callings appeared, but they do not appear in LDS Tools yet.

My ward also has this problem with LDS Tools on both Android and iPhone versions. When you select callings from the menu it lists YM and then YW underneath. When you select YM it shows the YM Presidency. When you select YW, the entire YW Presidency option is not listed. It starts with YW class advisers and then Laurels, Mia Maids and Beehives.

Our ward also has 2 Relief Society groups. Only "Relief Society 1" appears on LDS Tools. "Relief Society 2" does not appear on LDS Tools at all.

All of these callings are correct on LDS.org directory, LCR, MLS and CDOL.

Hopefully there will be a solution soon!

jasondavie wrote:Our ward also has 2 Relief Society groups. Only "Relief Society 1" appears on LDS Tools. "Relief Society 2" does not appear on LDS Tools at all.

We also have two Relief Societies. Under "Callings," it just shows "Relief Society 1," but if I tap on it it then shows both "Relief Society Presidency 1" and "Relief Society Presidency 2."

Oh yeah, duh! Mine does too, lol. But.....it still only shows the Relief Society 2 presidency and no other Relief Society 2 callings. What about yours?

However my YW presidency certainly does not show on LDS Tools at all

I think mine is the same as yours for Relief Society – only the presidencies show. I'm in a YSA ward so I can't duplicate the Young Women's Presidency problem.

Anyone have a unit name they would like to send me. Just so I can look into this for that unit?

actually I somehow missed this in the first post Provo YSA ward (163rd)

Well nevermind this is apparently really old ward. I think though its a bug in lds tools that they are working on.

jdlessley wrote:I can verify this is a problem.

My problem has been resolved. In this case it takes at least 24 hours from the time the changes appear in CDOL for them to show up in Android LDS Tools. One of the callings appeared in the sync I did 26 hours after the callings appeared in CDOL. The other showed up 28 hours later during that sync. Both callings were sent from MLS at the same time but took different amounts of time to show up - go figure.

My ward is Eight Mile Plains Ward in Eight Mile Plains Stake in Brisbane Australia.

I would love for the young women's presidency to appear again on LDS Tools!

Our ward lost the YM Presidency and a few scouting callings. All are in the desktop MLS. It started about 3 weeks ago. Very odd.

douggw wrote:Our ward lost the YM Presidency and a few scouting callings. All are in the desktop MLS. It started about 3 weeks ago. Very odd.

There were some cases where unit data didn't convert well during the recent CDOL upgrade and units will need to do some manual cleanup. If they aren't listed in CDOL (reflected in LCR, LDS Tools, and Directory), they will eventually disappear from MLS.

There are instructions on the LDSTech Wiki to correct duplicate or missing callings. I just made a minor update to those instructions.

jeffevannelson wrote:Anyone have a unit name they would like to send me. Just so I can look into this for that unit?

Hi Jeff,

you can look at our unit if you like.
0536830

scgallafent wrote: There were some cases where unit data didn't convert well during the recent CDOL upgrade and units will need to do some manual cleanup. If they aren't listed in CDOL (reflected in LCR, LDS Tools, and Directory), they will eventually disappear from MLS.

There are instructions on the LDSTech Wiki to correct duplicate or missing callings. I just made a minor update to those instructions.

This is not an issue of the callings not appearing in CDOL, for us all our callings appear fine in CDOL,
it is specifically an issue with the sync between CDOL and LDS Tools.

Correct. My situation is the same. CDOL and MLS both have the correct callings..in my case, the YM Presidency and some Scouting positions all are correct. It's just LDS Tools that doesn't have them. I read the wiki and did the "refresh" in MLS...Still the same. LDS Tools doesn't show any of the YM Presidency.

The product manager is aware of this issue and they are working on resolving it.

Any progress on this LDS Tools error?

Our ward leadership would really like to be able to view the YW presidency on LDS Tools.

All of our callings appear correctly on MLS, lds.org and CDOL.

Has there been a resolution or update with the YW presidency in LDS Tools?

I keep hoping..and syncing...and hoping...

Nothing yet

Me too lol! I haven't heard anything at all. I hope someone the solution is getting closer.

According to the LDS Tools for Android beta Google+ community,

That's slated for next week. It's a server side change and won't require a new release of LDS Tools. Sorry for the delay. There were a few things that needed to happen internally to get the service corrected. Another reason for the delay was that we have a 3 week freeze on releasing anything new around General Conference. Thanks for your patience.

https://plus.google.com/113677632101435 ... 1KybUGd6rG
(see comments)

We are experiencing the exact same issue in our Ward. Recommended steps above to correct did not resolve the issue. It is specific to YW Presidency. All information is correct in MLS. iPhone and Android apps are sync'd, and information is not included.

southpaw026 wrote:We are experiencing the exact same issue in our Ward. Recommended steps above to correct did not resolve the issue. It is specific to YW Presidency. All information is correct in MLS. iPhone and Android apps are sync'd, and information is not included.

This is a well known issue, as you could tell if you had read all the posts in this topic. The post just prior to yours explains that this is scheduled to be fixed in the coming week.