Date: Thu, 28 Mar 2024 22:37:31 +0000 (UTC) Message-ID: <1037188753.13.1711665451425@dfde8d0d273d> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_12_1801664052.1711665451425" ------=_Part_12_1801664052.1711665451425 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
# Mutabi= lity: always # Type: short # Allowed: 0-2 # The number of digits after the decimal that Mifos will carry for cashflow= warning threshold. AccountingRules.DigitsAfterDecimalForCashFlowValidations=3D2 # Mutability: always # Type: double # Allowed: 0 - 99 # The maximum allowable cashflow warning threshold. AccountingRules.MinCashFlowThreshold=3D0 # Mutability: always # Type: double # Allowed: 0 - 99 # The maximum allowable cashflow warning threshold. AccountingRules.MaxCashFlowThreshold=3D99 # Mutability: always # Type: double # Allowed: 150 - 1000 # The maximum allowable Repayment Capacity. AccountingRules.MinRepaymentCapacity=3D150 # Mutability: always # Type: double # Allowed: 150 - 1000 # The maximum allowable Repayment Capacity. AccountingRules.MaxRepaymentCapacity=3D1000 # Mutability: always # Type: double # Allowed: 0 - 50 # The maximum allowable Indebtedness Ratio. AccountingRules.MinIndebtednessRatio=3D0 # Mutability: always # Type: double # Allowed: 0 - 50 # The maximum allowable Indebtedness Ratio. AccountingRules.MaxIndebtednessRatio=3D50 # Mutability: always # Type: double # The Maximum MPESA Disbursal Limit #MPESA.DisbursalMax=3D50000
ISSUE: Surveys to Question Group data Migration issue= p>
ISSUE: Upgrading to 2.x logs contain error OR after upg= rade to 2.x enabling PPI gives error ERROR, org.hibernate.util.JDBC= ExceptionReporter, ?, ?, ?, Incorrect string value: '\xE0\xB2\x90\xE0\xB2\x= A6...'
Instructions for users, before upgrading from 1.6.x to 2.x AND This upgr= ade process can be applied after upgrading to 2.x also if you don't have an= y rows in these tables
STEP 1. Login to mysql as root,
STEP 2. Run this query
select t= able_name,table_collation,table_schema from information_schema.tables where= table_collation not like '%utf8%' and table_name like 'question%' and tabl= e_schema like '<MIFOS_DATABASE_NAME>';
STEP 3. If some rows are returned eg.
+------------------+-------------------+--------------+ | table_name | table_collation | table_schema | +------------------+-------------------+--------------+ | question_choices | latin1_swedish_ci | mifos | | questions | latin1_swedish_ci | mifos | +------------------+-------------------+--------------+
NOTE: if you get zero rows, given that you have used correct dat= abase name then you don't need to go to next step.
STEP 4. Run these queries to your Mifos database to cha= nge the character set of question tables from latin1 to be utf= 8
mysql>= ; use <MIFOS_DATABASE_NAME> mysql> alter table questions convert to character set utf8; mysql> alter table question_choices convert to character set utf8;
STEP 5. Verify using step 2, you should not get any row= s which are latin1 character set.
In previous versions of Mifos, if client approval is automatic, savings = accounts created during client creation were broken. Here is a query = you can run to determine if this has happened, and remove the incorrect acc= ounts.
Identify affected accounts:
SELECT s= a.account_id,a.global_account_num, a.customer_id FROM savings_account sa, a= ccount a where sa.account_id =3D a.account_id and a.global_account_num is n= ull;
Delete affected accounts (assuming no transactions have been logged for = the accounts):
delete f= rom savings_account where exists (select 'f' from account a where a.account_id =3D savings_account.account_id and a.global_account_num is null); delete from savings_performance where exists (select 'f' from account a where a.account_id =3D savings_performance.account_id and a.global_account_num is null); delete from saving_schedule where exists (select 'f' from account a where a.account_id =3D saving_schedule.account_id and a.global_account_num is null); delete from account where account.global_account_num is null;
If transactions have been created for these accounts, then ask for help = on the developer list.