When Center is moved to new Loan Officer, subordinate accounts are not updated

Description

When a center is moved from one loan officer to another, none (most?) of the
subordinate accounts (the customer, savings and loan accounts of the center, its
groups, or their members) are updated to reflect the new loan officer.

For reports that call for all loans of a given loan officer, Hussein said he had
to drill down from center->group->member-> account get all loans for a loan
officer, rather than using the loan's own personnel_id.

I think this is related to 1570 too.

I'll add detail as I verify it.

Environment

Platform: All, OS: All

Activity

Show:
bberning
May 12, 2008, 7:32 PM

Hi Chico, Sorry I wasn't more clear. Here's the situation: a few micro-finance
institutions have been using Mifos 1.0 for a while and have already moved
centers between loan officers. So now in their databases they have accounts
which do not have the correct loan officer and they will need to run a script on
the database to update all of those accounts with the proper loan officer id. I
am hoping that you or one of the software developers who worked on this issue
could provide the script, if possible. Thanks!

aliyaw
May 12, 2008, 9:13 PM

From my perspective, two things would be ideal:
1. A script which identifies and cleans up this issue which can be run by our
existing deployments (i.e. Jitegemea) until v1.1 ships and the underlying bug is
resolved.

2. (Lower priority) Potentially a similar script that is executed as part of the
upgrade scripts so that this issue is identified and cleaned up one final time
when Jitegemea and GK upgrade from their current versions to v1.1.

Definitely #1 would be very useful for Jitegemea immediately and they can always
run the same script one final time prior to upgrading if we don't want to do #2.

ccharlesworth
May 13, 2008, 1:56 PM

Created an attachment (id=645)
SQL Script which fixed problem at the database level

ccharlesworth
May 13, 2008, 1:58 PM

Hi Bart,

I've attached a SQL file (Issue1804_DatabaseFix.sql) which fixes this issue in
existing deployments.

Cheers
Chico

bberning
May 14, 2008, 10:09 AM

Thanks for the script Chico! I'll try it out today.

Fixed

Assignee

ccharlesworth

Reporter

bberning

Labels

URL

None

Story Points

None

Team

None

Scheduled For

None

Epic

None

Notify

None

productboard URL

None

Man Day Estimate

None

Components

Fix versions

Affects versions

Priority

Major
Configure