The way that maps get the data means that it will take a day or two for that data to flow there. If you see it correctly in LCR when you go back into it (or you can check in CDOL) then your update was successful.mevans wrote:I updated our ward's meeting time, as it's changing in 2016. I looked in Maps and still see the old time, and it's several hours after I updated it in LCR. As this is a new feature in LCR, I don't know if there's a problem, or if there is an overnight batch process that updates it. I'll check back tomorrow and see if it works then. I went back to LCR and see that it has the updated time.
Thanks for the info. It appears correctly on Maps today.jonesrk wrote:The way that maps get the data means that it will take a day or two for that data to flow there.
My update on Jan 1 was a coincidence, as opposed to waiting for Jan 1. I had the day off of work and remembered to check a few more church things. Actually, I'm surprised the church didn't send out an email reminder to clerks to verify and update the meeting time (unless such a reminder came through MLS). I don't know if it's the custom everywhere in the world to change meeting times the first of the year, but it's seemed common for our family members in the USA to do so. I just checked and other units in our stake still show the old meeting times. People probably need a reminder.russellhltn wrote:As an aside, I'd advocate for updating the meeting time as soon as both the new and old times have passed for the last Sunday in the year. No need to wait for the new year.
MLS had a way to set the next reminder date, and that would pop up a reminder (it might have been in urgent tasks) in MLS once the date was past. LCR doesn't currently have that option.mevans wrote:Actually, I'm surprised the church didn't send out an email reminder to clerks to verify and update the meeting time (unless such a reminder came through MLS).