Missing Person in Donors Add/Update
Posted: Sun Jul 18, 2010 11:00 am
EDIT: I finally found a thread with a very similar issue that indicates to give CHQ a call. http://tech.lds.org/forum/showthread.php?t=4351 I will do that and move along with the process of getting things fixed up. Please disregard!
I'm hopeful someone will have bumped into this before and my search skills are just lacking, but here it is...
We bumped into this the other day while doing a tithing batch. We tried to add a brother as a donor (his wife has typically done the tithing slips in the past), but it wasn't listing his name in the Select the Individual pop-up box. I've since tried to go in and add him as a donor in the Add/Update Donors task, same problem.
The brother is showing in the memberships, and when I pull up the Select the Individual box for the Membership side, it does show him there. (It also shows 327 members, whereas the Finance side shows only 326). I'd get fancy and send the records off someplace and request them back, but this brother HAPPENS to also be the Bishop. Any thoughts on what might resolve this particular issue? It wasn't *noticed* until after the latest 3.2 patch, but that doesn't mean it wasn't there before.
Sincerely,
Brian Lusk
I'm hopeful someone will have bumped into this before and my search skills are just lacking, but here it is...
We bumped into this the other day while doing a tithing batch. We tried to add a brother as a donor (his wife has typically done the tithing slips in the past), but it wasn't listing his name in the Select the Individual pop-up box. I've since tried to go in and add him as a donor in the Add/Update Donors task, same problem.
The brother is showing in the memberships, and when I pull up the Select the Individual box for the Membership side, it does show him there. (It also shows 327 members, whereas the Finance side shows only 326). I'd get fancy and send the records off someplace and request them back, but this brother HAPPENS to also be the Bishop. Any thoughts on what might resolve this particular issue? It wasn't *noticed* until after the latest 3.2 patch, but that doesn't mean it wasn't there before.
Sincerely,
Brian Lusk