Wife member, but Husband's IOS says she's not...

I had a case this weekend where a brother noticed on his IOS that his recently baptized "Current Spouse" was listed as "No" for the "Is a Member?" field.

His wife was baptized previously this year, has the same member number on her IOS as is listed on his IOS, but his IOS does not seem to link the "Current Spouse" to his baptized wife.

She may have been entered previously in the year as a non-member wife. When a member record was created after her baptism, it appears that the marriage information did not automatically get "updated" completely.

Questions:
(1) Is this a common occurrence?
(2) How does it get fixed? Do I have to terminate the marriage under the "Current Spouse" tab, and then re-add her as the "Member" for their marriage?

Thanks.

You might want to sent Headquarters this information through the MLS messages. (so that it's verified)_
Every once in a while, these updates will fall through the cracks. I would provide the record number of the spouse and the new member and they can submit a change request.
Jim

I don't remember what that MLS screen looks like. You might want to make sure you don't have two records for the same person. When you look at the husband's record, is there a record number for the wife? Does that record number contain your unit number suggesting it's a pseudo record number rather then a member record number?

Is her record correctly linked to the husband?

I contacted MLS Support and they mentioned that the records were fine and linked, but that when the wife was baptized and entered into the computer, the husband's record was not updated to say "YES" in the current "Is a Member" field of his IOS.

opee wrote:I contacted MLS Support and they mentioned that the records were fine and linked, but that when the wife was baptized and entered into the computer, the husband's record was not updated to say "YES" in the current "Is a Member" field of his IOS.

Ah. Hopefully they made a bug report so it has an opportunity to get fixed.

I just had the FTM's come to me for a "Part-member List" - a custom report printed the report, however, there were two families on the report tht fit this situation. That's why I signed up for this help, to see if I could get an answer to this problem. One has been like this for some time as the formerly non-member brother has been baptized, ordained a High Priest already. The other one was just last year where the couple married, then the non-member was baptized 4-5 days later, now ordained as an Elder. I cannot access the "Is a member?" field to change it.
John

jrrobinson wrote:One has been like this for some time as the formerly non-member brother has been baptized, ordained a High Priest already. The other one was just last year where the couple married, then the non-member was baptized 4-5 days later, now ordained as an Elder. I cannot access the "Is a member?" field to change it.

I would assume that the "Is a member" field is worked out from the baptism information. Check the record to make sure that the baptism and confirmation is recorded on his record.

Also check the record number. If it contains your unit number in it, then it's not his real record - you're still using his "place holder" record from when he was a non-member spouse.

A few things you can try:

- Do a "member refresh". That might clear some things up. I'm not sure how long you have to wait, I'm sure it's at least a few hours from the first send/receive until the refresh arrives.

- Do a backup and restore using MLS's backup. That forces MLS to rebuild the indexes.

- If all else fails, do a "special request" on his record and explain to SLC about the problem.

jrrobinson wrote:I just had the FTM's come to me for a "Part-member List" - a custom report printed the report, however, there were two families on the report tht fit this situation. That's why I signed up for this help, to see if I could get an answer to this problem. One has been like this for some time as the formerly non-member brother has been baptized, ordained a High Priest already. The other one was just last year where the couple married, then the non-member was baptized 4-5 days later, now ordained as an Elder. I cannot access the "Is a member?" field to change it.

Another thing to check is to make sure there is only one record for these members. When a non-member record exists in MLS, the creation of a new member record doesn't automatically remove the non-member record. You might have two records in MLS for these brethren, in which case you can just delete the non-member record.

Alan_Brown wrote:Another thing to check is to make sure there is only one record for these members. When a non-member record exists in MLS, the creation of a new member record doesn't automatically remove the non-member record. You might have two records in MLS for these brethren, in which case you can just delete the non-member record.

It sounds to me like you have a non-member record of the individuals. There is a menu option for "Remove Non-member Record". Use this to remove the record as Alan_Brown suggested, and it should take care of the problem.

Alan_Brown wrote:When a non-member record exists in MLS, the creation of a new member record doesn't automatically remove the non-member record.

There's also no guarantee that the new member record has found it's way to your ward. I'm quite sure the membership record is processed like any other convert - through the mission. Errors have been known to happen.

And it might be that the record hasn't replaced the old non-member record - that's why I suggested you look at the record number and possibly do a refresh.

RussellHltn wrote:A few things you can try:

- Do a "member refresh". That might clear some things up. I'm not sure how long you have to wait, I'm sure it's at least a few hours from the first send/receive until the refresh arrives.

- Do a backup and restore using MLS's backup. That forces MLS to rebuild the indexes.

- If all else fails, do a "special request" on his record and explain to SLC about the problem.

My assumption is that in these cases the member's record simply never got refreshed from CHQ when the non-member spouse was baptized. Before doing any of the above, I would make a simple change to the affected member's record, transmit it to CHQ, and then when you receive confirmation back via MLS that the change was recorded, change it back (if necessary) and re-transmit it again to CHQ. Each time you get a confirmation of the change back from CHQ it should refresh the member's record.

Some innocuous changes you can make are changing the preferred name (like from John to Johnny) or changing the state of the birth or marriage place from a full spelling to an abbreviation or vice versa (like from Utah to UT). Most likely it is recorded correctly at CHQ and you just need something simple like this to trigger a refresh of the affected member's record.

jbh001 wrote:Before doing any of the above, I would make a simple change to the affected member's record, transmit it to CHQ, and then when you receive confirmation back via MLS that the change was recorded, change it back (if necessary) and re-transmit it again to CHQ. Each time you get a confirmation of the change back from CHQ it should refresh the member's record.

That would work only if the record being modified has a real record number and not the temporary one that contains the unit number. Hmmmm. I wonder if that's how the whole problem got started ...

RussellHltn wrote:That would work only if the record being modified has a real record number and not the temporary one that contains the unit number. Hmmmm. I wonder if that's how the whole problem got started ...

If it is not a "real" record number, then it is impossible to change the state from an abbreviation to the full spelling (or vice versa; i.e. UT to Utah) since places are not recorded on the local/temporary/administrative records (as shown in this example of a "real" record from the test data). Also, those local/temporary/administrative records have no place to show who the spouse is, let alone whether or not they are a member (as shown in this example of a local/temporary/administrative record from the test data).