Page 1 of 1

LCR equivalent to Membership Transaction Report?

Posted: Sat Dec 03, 2016 7:13 pm
by cspinfo@telus.net
Is there any work being done on a reporting capability in LCR that's equivalent to the Membership Transaction Report? Will it be part of the "cleanup" features in the next LCR project beginning in January?

Our unit was very sad to lose the Membership Transaction Report when it was discontinued in MLS ver 3.8.5

We found it EXTREMELY useful to track change specifics for several reasons:

1. The specifics of any change are listed, including the data that's been added/changed. e.g. an address on a move-out, or the person who performed an ordinance (or their birthdate/MRN), or a correction of birthdate/place or marriage date/place.

2. The date & source of the change are listed.

3. We have encountered data loss/corruption in MLS in the past & have had to try & find evidence for the changes/additions to re-enter them in MLS. (e.g. baby blessings, children of record, baptisms, ordinations, etc., etc.) This critical data is READILY available if the Membership Transaction Report was printed & retained, at the time it was produced. If not, leaders can spend endless hours trying to find some other evidence/source for the missing/corrupt data. I anticipate that this will happen occasionally in LCR also, and sincerely hope that a similar report will be available in LCR to help us in such situations.

So, despite the Membership Transaction Report being discontinued in MLS v3.8.5, it's loss is sorely missed in our unit! :cry:

Furthermore, we would GREATLY appreciate an equivalent be available in LCR (automatically produced would be ideal but we'd take manual if that's the only possibility), which doesn't currently exist. :D

Re: LCR equivalent to Membership Transaction Report?

Posted: Wed Mar 22, 2017 6:51 pm
by chancerichardson
A report or a last-updated when/who tag on the record is something that I am finding is urgently required. Yes, only a few people have access to make changes, but we all make mistakes in one form or another, and so does the system.

As an example: Within the past two weeks a number of home teaching assignments in my ward were wiped out. Coupled with that, a number of members and families quorum assignments were changed at some point in the past few months. In both cases no one recalls making any changes, but we have no way of validating who/how/why/when.

Please!!!!!!

Re: LCR equivalent to Membership Transaction Report?

Posted: Sat May 06, 2017 11:56 pm
by cspinfo@telus.net
chancerichardson wrote:A report or a last-updated when/who tag on the record is something that I am finding is urgently required. Yes, only a few people have access to make changes, but we all make mistakes in one form or another, and so does the system.

As an example: Within the past two weeks a number of home teaching assignments in my ward were wiped out. Coupled with that, a number of members and families quorum assignments were changed at some point in the past few months. In both cases no one recalls making any changes, but we have no way of validating who/how/why/when.

Please!!!!!!
Totally agree but the forum is strangely silent on if/when this data may become available to clerks. Who at LCR project management can tell us?

Re: LCR equivalent to Membership Transaction Report?

Posted: Sun May 07, 2017 7:08 am
by eblood66
cspinfo@telus.net wrote:Totally agree but the forum is strangely silent on if/when this data may become available to clerks.
The forums are almost entirely just user-to-user help. It is not a mechanism to provide feedback to the product managers (use the Feedback link in LCR or on the lds.org main page for that) or a way to get information about future development plans. Occasionally, a developer or product manager gives us some hint of things to come but that's very infrequent.
cspinfo@telus.net wrote:Who at LCR project management can tell us?
There is no way to get two way communication about future plans. The church just doesn't do that. You can use the feedback link to make suggestions but you won't get a response about when or if it will be implemented.