Presently, I see no capability for entering, viewing, or printing geocodes in LCR.I am hoping that provisions for geocoding and Custom Reports will be enhanced as LCR is further implemented. Nevertheless, I am looking forward to using LCR.

RichardGamble wrote:Will I be able to create these Custom Reports in LCR when MLS is retired? I do not like the idea of telling leaders, "Sorry, I cannot help you." Thank you.

I'm a huge fan of MLS for it's custom report ability. While I wish for the best, I also think the loss of MLS will mean a loss of customization for reports, and the ability to search membership records on custom criteria, similar to the ability to export data from MLS currently is becoming more limited.

(Added later: I don't fault anyone for this, but see that the current push is for other functionality with their limited programming resources. Developers may get around to making a "customization" option for reports in LCR later?)

mevans wrote:Will the historical HT/VT visit data be loaded in LCR, or will we have to do reports from both systems for a year if we want to see if a family has been visited?

Data is migrated from MLS. There is a brief window between when the last MLS transmission was made and when the data is migrated where data entered in MLS won't make it to LCR. For units that transmit regularly, that window should only be fairly shortly.

Related directly to this post, I would love for the custom reports to all be moved online to LCR so I can run and input data from home rather than from only the church building. (It would be ideal if the user defined data could be exported or synced so that it is in LCR.)

Currently, my custom reports that have user defined fields (which I use for keeping track of who spoke and prayed in Sacrament meeting) are all broken with an error that says "Changing the calling in organization selection invalidates the calling position"; however nothing in the reports I am trying to run use any calling fields or selectors. So there is a bug with the custom reports. Please fix this!