Out of Unit Callings not going away

[stanmoore1]

They are fixed now. Thank you!

[Biggles]

Hi,

I just wanted to report an issue we are having with the Callings section in the Leader and Clerk Resources page. We have a few Out of Unit callings that won't go away, even after several weeks for some and over a month or two for others. One is listed as a full-time missionary. A unit refresh on our end did not solve the problem.

Thanks!

I have the same issue with a sister (Relief Society 1st Counseller) who moved in from Portugal. Her records were requested by us in April 2011, but she still remains listed in the Out of Unit Callings list, for her old unit. I've done all the usual unit data refresh for duplicate callings etc.. Any further advice out there?

[BrobergMW]

I want to correct some misunderstanding about Out-of Unit Callings in MLS, CDOL and LDS.org.

1. There is no cross-population between one ward's (or branch's) MLS assignments and another's. If an assignment appears under a ward or branch in "Show all assignments" in CDOL, that assignment was previously entered in that unit's MLS and then removed from visibility in MLS through one of several possible methods. For ecclesiastical organizations, both custom positions (displayed in green) and standard positions (displayed in black), visible in CDOL under "Show all positions," are usually only entered in MLS, and therefore should be removed in MLS if possible. Item 2 describes the normal process for viewing and removing incorrect assignments no longer visible in MLS.
2. The correct process for removing incorrect out-of-unit callings (or other duplicate or historical callings) that erroneously show in either CDOL and/or LDS.org, but not in the current MLS, is to have a CDOL refresh pushed down to the unit (not a refresh requested from the unit). The unit would then transmit from within MLS to receive the refresh, after which a clerk or someone with MLS assignment edit rights would go to the incorrect assignments and remove them as needed. Once only correct assignments are showing, the unit would transmit the corrections back to headquarters, which would update CDOL and eventually LDS.org.
3. If, after the downloaded refresh from CDOL is retreived, MLS still does not display the incorrect assignments, the unit would then need to contact MLS support so that a technician can take control of the unit's MLS computer and check the backend local unit database for hidden assignment artifacts. If those exist the technician can remove them and then the fixed data can be transmitted to update the other applications.
4. On rare occasions the incorrect information might only show on LDS.org. That may be due to timing, where the LDS.org data has not yet been updated after a data entry in CDOL or MLS. That issue is usually corrected by waiting a day or two. If the data still only appears in LDS.org after sufficient waiting, an administrator for LDS.org might need to be notified.

The above information has been validated by testing and research. Examples that fall outside of the above are welcomed and should be sent to oiservices@ldschurch.org.

[jonesrk]

1. There is no cross-population between one ward's (or branch's) MLS assignments and anothers. If an assignment appears under a ward or branchin "Show all assignments in CDOL, that assignment was previously entered in that unit's MLS and then removed from visibility in MLS through one of several possible methods. For ecclesiastical organizations, both custom positions (displayed in green) and standard positions (displayed in black), visible in CDOL under "Show all positions," are usually only entered in MLS, and therefore should be removed in MLS if possible. Item 2 describes the normal process for viewing and removing incorrect assignments no longer visible in MLS.

The problem is that in the Clerk resources they do display the callings in Out of Unit Callings from other wards. So when someone moves, if that calling doesn't get removed correctly then the old calling stays in CDOL, and the new ward's clerk can't clean up the calling.

[jdlessley]

There is no cross-population between one ward's (or branch's) MLS assignments and anothers.

This is true. However, the link of data between one unit's MLS and another unit's MLS is displayed on the LDS.org directory. The linking key is the membership number for the member with an out-of-unit record. The clerk for the unit in which the membership record resides has no control over the out-of-unit record since it is in another unit's MLS. Since out-of-unit records are temporary records they are not automatically removed when a member moves.

[BrobergMW]

The link of data mentioned does exist, but only for LDS.org, not for one unit's MLS to another, nor for a unit's CDOL to another. LDS.org does not push information from one unit's MLS to another unit's MLS, nor from one unit's CDOL to another unit's CDOL. Some prior comments in this thread make it sound like entries in one unit's MLS or CDOL ("Show all assignments") are the result of another unit's MLS entries, which is not so. The only assignments at present that a unit will see in MLS or CDOL are those that have been entered in that unit's MLS or CDOL, while on LDS.org a home unit will see an assignment entered from another unit because the assignment was entered using a member's record number. For this reason, wards or branches need to stay on top of any out-of-unit callings (or active callings assigned to moved-out members that might be stuck in the system) and properly release the individuals in MLS when they have completed their service so that the current home unit is not carrying assignment discrepancies on the LDS.org site, over which the home unit has no control to change in MLS or CDOL.

While I can see the benefit of displaying this information on LDS.org, perhaps the communication between the website and the two feeding applications of MLS and CDOL should be reviewed to consider if one unit's failure to release individuals from callings in MLS should continue to affect the accuracy of the home unit's LDS.org callings list, besides the other unit's callings list. Actually, to me it doesn't seem that big of an issue, as the callings list for any given unit is only visible to a limited number of individuals (it's not like the issue is announced at general conference or broadcast in the media). The biggest issues are that it displays inaccurate information (and we always strive for accuracy) and that the inaccuracy is not controllable by half of the group it affects.

The possible edit tools for the callings list on LDS.org, mentioned by Ryan, may be just the ticket for resolving this issue.

[jdlessley]

Some prior comments in this thread make it sound like entries in one unit's MLS or CDOL ("Show all assignments") are the result of another unit's MLS entries, which is not so.

Posts to these forums, I think, is a good indication of the level of understanding that exists in the community. If there are but a few who post to these forums with this misunderstanding about how data is handled then imagine how many more who have the responsibility to keep MLS data up to date are not aware of the affect of their recording keeping habits. To have one clerk who is keeping on top of his unit's records and then have one or more other units that do not or can not do the same adversely affect the data of the former is frustrating at the least.

For this reason, wards or branches need to stay on top of any out-of-unit callings...

There are some who are aware of this. But I would venture a guess that there is a very high percentage of that are not for various reasons. Information like this needs to be in front of those who are not aware of the impact they could be creating outside their own unit. Nowhere other than these forums has this information been presented. So if there is a small number of forum users who are aware of this just imagine how many units out there are not aware.

[lajackson]

So if there is a small number of forum users who are aware of this just imagine how many units out there are not aware.

Perhaps we could have an Out of Unit Calling Awareness Day. Or the stake clerk can keep it on the list of things he does when he goes around to visit units during the year. [grin]

For me, I am hoping that upcoming editing tools will allow the receiving unit to solve the problem.

[stanmoore1]

Actually, to me it doesn't seem that big of an issue, as the callings list for any given unit is only visible to a limited number of individuals (it's not like the issue is announced at general conference or broadcast in the media). The biggest issues are that it displays inaccurate information (and we always strive for accuracy) and that the inaccuracy is not controllable by half of the group it affects.

This issue could delay or prevent a new member from getting a calling. For example, someone with an out-of-unit calling won't show up on the Members without Callings report. If leadership is not aware of this issue, they may skip over this member when looking for potential candidates because they are trusting the Members without Callings report. Of course, if they are aware of this issue, they can check to see if anyone has an out-of-unit calling and add them to the list.

[ckellsworth]

The correct process for removing incorrect out-of-unit callings (or other duplicate or historical callings) that erroneously show in either CDOL and/or LDS.org, but not in the current MLS, is to have a CDOL refresh pushed down to the unit (not a refresh requested from the unit). The unit would then transmit from within MLS to receive the refresh, after which a clerk or someone with MLS assignment edit rights would go to the incorrect assignments and remove them as needed. Once only correct assignments are showing, the unit would transmit the corrections back to headquarters, which would update CDOL and eventually LDS.org.

How does one go about requesting a refresh pushed down by CDOL? IIRC there is that option within MLS to request refresh but that does not sound like what your talking about.