New Data into Directory

I am looking to see if anyone else has experienced this situation:

We have a new YSA ward in our stake that was converted from a branch outside our stake. The ward shows up under both the new.lds.org and the LUWS. I am seeing a problem with the leadership directory on new.lds.org -- All it shows is the bishop. New members are showing up in the Families section.

It was my understanding that this information is populated through MLS. I know their MLS system is populated with more than just the bishop and they have had no problems transmitting.

I have also noticed that the time listed under LUWS is incorrect. This was changed the week before Conference. I know it takes some time before the time changes because I have read several discussions.

Young Single Adults are very tech savvy and I am trying to get this information updated quickly.

Should I just sit tight or should I be doing something more?

Regarding the Leadership issue -
new.lds.org grabs that information from CDOL
which had a bug sometime in the past communicating
with MLS. You'll want to log in to cdol.lds.org and
click on "All Callings" for the YSA ward to see if the
rest of the Bishopric is populated there or if MLS updated the Bishopric
during the bug-period. If not, then you click on
Feedback, select Other as type, select Information Change
as a subtype, and then let them know who was called to
which positions and they will manually update it for you.
Once changed in CDOL, it will move over to mls.lds.org.
They are pretty responsive over at cdol.lds.org - shouldn't
take more than a few days at most.

Regarding the time issue for the unit
The "activation date" you use to say when the times go into
effect has to be in the future (sometimes 2 Sundays into the future)
or the trigger at CHQ won't be set. Also don't forget to transmit
immediately following the setting of time. There was a least one thread
about setting unit times for LUWS, I'm sure one of the moderators can
point you to them.

- Atticus

atticusewig wrote:Regarding the Leadership issue -
new.lds.org grabs that information from CDOL which had a bug sometime in the past communicating with MLS. You'll want to log in to cdol.lds.org and click on "All Callings" for the YSA ward to see if the rest of the Bishopric is populated there or if MLS updated the Bishopric during the bug-period. If not, then you click on Feedback, select Other as type, select Information Change as a subtype, and then let them know who was called to which positions and they will manually update it for you. Once changed in CDOL, it will move over to mls.lds.org. They are pretty responsive over at cdol.lds.org - shouldn't take more than a few days at most.

I called Local Unit Support just two days ago on this very topic. I had called previously and received advice such as Atticus just mentioned, and that will probably still work. But Support told me in this case that I should fix it from the MLS side. I was to edit each calling somehow (the easiest way is to change the "set apart" flag to be the opposite, then save, then set it back and save. That will trigger the calling information to be sent to CDOL. You can experiment with just a couple of callings and make sure it works before going through the process of doing that for all the callings. It did indeed work for the ward I was working with, which only had about half their callings in CDOL until we ran through this process.

However, that process is tedious, so if the Information Change request on CDOL works, that's much easier to do.

atticusewig wrote:Regarding the time issue for the unit:
The "activation date" you use to say when the times go into effect has to be in the future (sometimes 2 Sundays into the future) or the trigger at CHQ won't be set. Also don't forget to transmit immediately following the setting of time. There was a least one thread about setting unit times for LUWS, I'm sure one of the moderators can point you to them.

There is no such thing as an "activation date"; there is only the date of the next reminder (which clearly should be in the future). This is explained on the wiki under Edit meeting times.

atticusewig wrote: Regarding the time issue for the unit
The "activation date" you use to say when the times go into
effect has to be in the future (sometimes 2 Sundays into the future)
or the trigger at CHQ won't be set. Also don't forget to transmit
immediately following the setting of time. There was a least one thread
about setting unit times for LUWS, I'm sure one of the moderators can
point you to them.

You can also check the meeting times in CDOL to make sure that they match what is in MLS. If they are the same then it should make it to LUWS (it may take up to 2 days). If they aren't the same you need to change them in MLS save it and then change them back to the correct time. That should get them sent up again to CDOL.

mzundel wrote:It was my understanding that this information is populated through MLS.

That is correct. MLS sends the callings up to CDOL. And the directory gets its data from CDOL.

mzundel wrote:I know their MLS system is populated with more than just the bishop and they have had no problems transmitting.

I hate to question this but how do you know? Have you looked at their MLS? If the ward we are talking about is the Roy YSA Ward, then I don't think they have put any callings in yet. I looked a a backup from Sep 28 and it only has the bishop there, and in all the files sent from MLS to CDOL there aren't any more callings added.

If I've got things all wrong and they really do have data in MLS then let me know and we can see what more we can do to get the data into CDOL.

Alan_Brown wrote:It did indeed work for the ward I was working with, which only had about half their callings in CDOL until we ran through this process.

However, that process is tedious, so if the Information Change request on CDOL works, that's much easier to do.

One other option that is available from within CDOL (to those with the correct rights, which I think Support should have) is to have CDOL request a complete pull of the MLS callings.

ryan jones wrote:One other option that is available from within CDOL (to those with the correct rights, which I think Support should have) is to have CDOL request a complete pull of the MLS callings.

That's the process I went through with one ward a couple of months ago, and it was easy and very effective. It certainly makes sense, since the problem is clearly one where information correctly entered into MLS is somehow not getting to CDOL.

But two days ago when I called Support regarding the same problem with a different ward, the person I was talking to (who then consulted with his manager), either didn't know how to do that or was unwilling to do so. I persisted in saying that I knew there was an easier way that they could do from their end, but they just kept telling me to do it from the MLS end (even though the pure MLS technique is very tedious and it could be easy to miss a variety of callings, so I certainly do not recommend it).

I recount this experience not to complain, but simply to advise others that they may need to be very persistent in order to get Support to have CDOL request a complete pull of the MLS callings. But that persistence will be worth it.

ryan jones wrote:One other option that is available from within CDOL (to those with the correct rights, which I think Support should have) is to have CDOL request a complete pull of the MLS callings.

How about a suggestion for the CDOL? Make it possible for a few key individuals (Bishop, Ward Clerk, Stake Pres, Stake Clerk) to logon to the CDOL and check a box that would cause CDOL to perform this "complete pull" of MLS callings.

This would save a call to CHQ and could be done on a weekend.

techgy wrote:How about a suggestion for the CDOL? Make it possible for a few key individuals (Bishop, Ward Clerk, Stake Pres, Stake Clerk) to logon to the CDOL and check a box that would cause CDOL to perform this "complete pull" of MLS callings.

This would save a call to CHQ and could be done on a weekend.

After Alan's post I thought of the same thing. I was going to suggest it. I was thinking along the lines of the STS, but I could see those that you listed being wise too.