I recently checked the stake quarterly report and a couple units were showing zeros in their columns. When I logged into that unit's MLS (same day, same building) their 1st quarter numbers were showing up just fine.
Any idea what would be causing this discrepancy?
Quarterly Report Stake/Ward not matching
-
- New Member
- Posts: 17
- Joined: Mon Mar 10, 2008 1:38 pm
- ffrsqpilot
- Member
- Posts: 247
- Joined: Fri May 09, 2008 8:51 am
- Location: Montrose, Colorado
My first guess is that they (the wards in question) have done the report and hit the send/receive button but you (if you are on the stake computer) may not have done a send/receive yet. Try clicking on send/receive and then check the quarterly report. The wards in question should then show data in their columns.
If that doesn't work then you are beyond my expertise and hopefully one of the moderators here can help you out.
Jim
If that doesn't work then you are beyond my expertise and hopefully one of the moderators here can help you out.
Jim
- aebrown
- Community Administrator
- Posts: 15153
- Joined: Tue Nov 27, 2007 8:48 pm
- Location: Draper, Utah
As pilotfly mentioned, someone may not have done a send/receive. What really needs to happen is:natrx wrote:I recently checked the stake quarterly report and a couple units were showing zeros in their columns. When I logged into that unit's MLS (same day, same building) their 1st quarter numbers were showing up just fine.
Any idea what would be causing this discrepancy?
- The ward fills out the quarterly report.
- The ward does a send/receive.
- After the ward information is received at Church Headquarters, some time needs to pass before the data is available for download by the stake. I believe I heard once that this is about 4 hours, but that was quite a while ago, and this lag may be shorter now. Perhaps DJC or some other Church employee can clarify this.
- The stake then does a send/receive.
- childsdj
- Member
- Posts: 258
- Joined: Wed Feb 07, 2007 9:51 am
This was actually, if I remember correctly, a problem with 2.8.1 and one of the main reasons that 2.8.2 was released. It sounds exactly like the situation you described. The data is intact and correct but was showing zeros in the report. I believe it is fixed in 2.8.2 so make sure you are running with that version and see if the problem goes away.