Re: Does the changes in apache fineract platform necessary to fix FINERACT issues

Hi Markus, There is a limitation in implementing this in the backend. In the database, we are storing only the "classification_enum" in the "acc_gl_account" Classification Enum has the following values for respective account types. ASSET - 1 LIABILITY - 2 EQUITY - 3

Re: Does the changes in apache fineract platform necessary to fix FINERACT issues

Hi Markus, Exactly, it should be independent from the client. At the moment account in charts of accounts are ordered using orderBy directive. I will send the response from the platform ordering them as expected in this issue. Cheers! Thanks

Does the changes in apache fineract platform necessary to fix FINERACT issues

Hi devs, Just a little bit of misunderstanding. Let's take an example. The ticket at [1] requests to arrange the accounts that fall under one account type in order of their GL codes. This could be done easily with the changes at [2]