Tech Forum

pze wrote:The directory of members still shows "secondary telephone number" information, even though this field no longer exists. That is why I could not find the information on the individual/household records, but it showed up on the directory of members. Basically the last line of information on the household record is bad (if there was a secondary telephone number recorded). Local Unit Support said that the problem will probably be fixed in MLS 3.2, which is due out in the fall.

Meanwhile I won't be using the directory of members.

Is there any way to delete this information if it shows up, or are we stuck until MLS is fixed and just need to quit using the directory of members?

...Am having same problem with our 3.1.5 MLS "Directory of Members".

...Can't delete or change any of these "spurrious" phone numbers or
"Do Not Contact" labels.

Glad I searched before asking same question.

I now have MLS 3.2.1 and the problem has not been fixed (second phone numbers still exist). I emailed SLC asking about the problem and when it will be fixed because I thought the problem would be fixed with MLS 3.2.

It is quite a bit of work, but you might consider moving the affected records out of the unit, and then back in again. It should wipe the contact info clean.

After a boundry realignment, our ward was moved to a new stake, but for some reason, people who had a stake calling in the former stake were still being listed in the members with callings section and couldn't be released. The former Stake, the current Stake, and CHQ all tried to help but to no avail.

Just make sure that before you move each record or household you capture the following information that you will need to enter again:

• All current (accurate) contact info - including the proper telephone
  numbers, emails addresses, postal addresses, and geocodes.
• Stake and unit callings held
• Home teaching info - who is member's companion, to what HT district he is assigned, and the families hometaught. Also the companionship assigned to hometeach the records moving out.
• Visiting teaching info - who is member's companion, to what VT district she is assigned, and the sister visit taught. Also the companionship assigned to visit teach the records moving out.

You will also need to relink the records to any previous donor records when the records come back into the unit.

I recommend moving them out of your current Stake to make sure the records are completely scrubbed of contact info. That's what I did.
Moved the records, waited an hour, then requested the records back into the ward. You don't have to wait for CHQ to send you confirmation the records moved before you request them back; Once you send the move request to CHQ, most of the information listed above is cleared.

It is a lot of work, but it might just well be worth it to be able to use the Directory of Members again.

- Atticus

atticusewig wrote: After a boundry realignment, our ward was moved to a new stake, but for so me reason, people who had a stake calling in the former stake were still being listed in the members with callings section and couldn't be released. The former Stake, the current Stake, and CHQ all tried to help but to no avail.

This is a known bug in MLS/CDOL. We are working to fix the CDOL part of the problem now. MLS has it on their plate as well. They are just trying to finish up any CUBS related issues.

Once both systems have the fixes in place then a ward moving to a different stake will be handled correctly.

ryan jones wrote:This is a known bug in MLS/CDOL. We are working to fix the CDOL part of the problem now. MLS has it on their plate as well. They are just trying to finish up any CUBS related issues.

Once both systems have the fixes in place then a ward moving to a different stake will be handled correctly.

Will the fix also correct callings in units that have already moved? Or is the fix described by atticusewig the only way to deal with problems that already exist?

eblood66 wrote:Will the fix also correct callings in units that have already moved? Or is the fix described by atticusewig the only way to deal with problems that already exist?

We will need to make sure that the problem can be fixed with a full refresh.

I think that for now there might be something the programmers can do to clean out the old stake info so that a refresh of the stake info would work. If that works we will need to let the support staff know the fix so that they can do it when people call in.