Tech Forum

We recently split our ward. I was the ward clerk in the former combined ward and am the ward clerk in the newly formed ward. Prior to the split, all our households had verified locations. However, after the split, all households in the new ward have an "unverified location" status now. Do I have to click on every household (109 of them), click 'edit', then change the status? That's a huge time sink. I'm not sure why families suddenly became unverified.

Is there any way to "batch" process them all?

I wanted to print a new ward map but don't want all the '!' on them.

I also want the names on the households but it looks like that feature was taken away. (I noticed that on another post).

sasgrw wrote:I'm not sure why families suddenly became unverified.

Forming a new ward or households moving into another ward due to a boundary realignment is the same as if the household physically moved to a new ward. Realignment moves and new unit creation associates the household with a new unit number. It is the association of the household with a new unit number that triggers the change in the verified status.

I can understand the frustration in having to verify a large number of households for this situation. And no, there is no way to batch process households. They must be done individually.

How did you move the members to the new unit?
1) With the Boundary Realignment option in MLS? If so which version.
2) With the Move Records after Boundary Realignment option in Clerk Resources?
3) Some other way?

Even though the unit changed I agree that it shouldn't cause the households to become unverified.

I used MLS, not the website. I'm not sure which version we have. I'd have to check on Sunday, but it updates automatically so it should be the latest version.

I don't know if anyone will see a reply posted so long after the previous reply, but I'll try posting here and in a new thread, also. When a boundary change like this is made, does LDS Maps forget custom locations where the clerk has moved a household? Or does it just change the flag from verified to unverified without changing the location?

In units in Thailand, I believe the problem is worse, because the household becomes an unmapped household. This is worse because it takes a fair bit of time to map each household, far more than just verifying the location. In Thailand every household is unmapped by default.

Since returning from an MLS mission with my wife, I have continued to help senior missionaries serving there and I have tried to talk to developers to discuss why custom locations disappear. It seems that when a clerk makes any change to an address, (even changing the order of the street address and apartment number) the custom location is forgotten by LDS Maps.

JimRedd wrote:It seems that when a clerk makes any change to an address, (even changing the order of the street address and apartment number) the custom location is forgotten by LDS Maps.

Has that changed? It used to be that moves within a ward didn't move the marker. That's far worse, since the maker would be on the last location and not the current one - with nothing to indicate that it might no longer be accurate.

So, while I understand the frustration it causes, until such time as the system can detect between a move and a simple fix, having it become unverified/unmapped due to a change is the lessor of two problems. At least you can see what addresses needs attention and not have to re-verify the entire ward because you can't be sure what's accurate anymore.

russellhltn wrote:It used to be that moves within a ward didn't move the marker.

From recent personal experience I can say that a move within a ward does move the marker and sets the location to unverified (at least when the address can be geocoded).

Same thing a happened in our ward when we had boundary changes. I was a clerk in the old ward. As EQ president now, I think it has its benefits. I can go through and identify who I need to follow up on. However, I also wish that any leadership position, not just clerks, could mark the location as verified. I don't think very many families will get verified for now. I guess I could submit that through website feedback.