[jira] [Commented] (FINERACT-389) Arrange the accounts that fall under one account type in order of their GL codes
[ https://issues.apache.org/jira/browse/FINERACT-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963344#comment-15963344 ] Thisura commented on FINERACT-389: -- There is a limitation in implementing. 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. {code} ASSET - 1 LIABILITY - 2 EQUITY - 3 INCOME - 4 EXPENSE - 5 {code} The values can't be used to reflect the ascending order of names. Therefore ORDER BY "classification_enum" won't work in the sql query. There fore we have two options. * Write a sorting function to sort the result set based on the classification_enum and then on gl_code. * Change the classification_enum values to reflect the ascending order of account types and add ORDER BY classification_enum ASC, gl_code ASC The changed enums will look like follows. {code} ASSET - 1 LIABILITY - 5 EQUITY - 3 INCOME - 4 EXPENSE - 2 {code} > Arrange the accounts that fall under one account type in order of their GL > codes > > > Key: FINERACT-389 > URL: https://issues.apache.org/jira/browse/FINERACT-389 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: p2 > > Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2825 > Original Description: > Accounts in chart of accounts are arranged by their account type but those > accounts in the specific account type are randomly arranged. > I was recommending for the accounts in the same account type to be arranged > by their GL code. Since the relating accounts will be under one header and so > their GL codes will be following each other and bring presentable > arrangement. (accounts in the same header, their GL codes should have > relation) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-389) Arrange the accounts that fall under one account type in order of their GL codes
[ https://issues.apache.org/jira/browse/FINERACT-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963335#comment-15963335 ] Thisura commented on FINERACT-389: -- In the above PR https://github.com/openMF/community-app/pull/2157 the fix will work only in the community-app. However as discussed in the thread "Does the changes in apache fineract platform necessary to fix FINERACT issues", it is suggested to implement these kinds of changes in the backend, to decouple the front-end. New PR sent at https://github.com/apache/incubator-fineract/pull/330 to incorporate this into the backend. > Arrange the accounts that fall under one account type in order of their GL > codes > > > Key: FINERACT-389 > URL: https://issues.apache.org/jira/browse/FINERACT-389 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: p2 > > Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2825 > Original Description: > Accounts in chart of accounts are arranged by their account type but those > accounts in the specific account type are randomly arranged. > I was recommending for the accounts in the same account type to be arranged > by their GL code. Since the relating accounts will be under one header and so > their GL codes will be following each other and bring presentable > arrangement. (accounts in the same header, their GL codes should have > relation) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-389) Arrange the accounts that fall under one account type in order of their GL codes
[ https://issues.apache.org/jira/browse/FINERACT-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963303#comment-15963303 ] ASF GitHub Bot commented on FINERACT-389: - GitHub user ThisuraThejith opened a pull request: https://github.com/apache/incubator-fineract/pull/330 Fix FINERACT-389 ordere by gl_code added to sql query in retrieveAllGLAccounts You can merge this pull request into a Git repository by running: $ git pull https://github.com/ThisuraThejith/incubator-fineract FINERACT-389 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-fineract/pull/330.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #330 commit 1b438021421f6f64414cc5889735987a622f1f3a Author: ThisuraThejith Date: 2017-04-10T18:32:02Z ordere by gl_code added to sql query in retrieveAllGLAccounts > Arrange the accounts that fall under one account type in order of their GL > codes > > > Key: FINERACT-389 > URL: https://issues.apache.org/jira/browse/FINERACT-389 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: p2 > > Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2825 > Original Description: > Accounts in chart of accounts are arranged by their account type but those > accounts in the specific account type are randomly arranged. > I was recommending for the accounts in the same account type to be arranged > by their GL code. Since the relating accounts will be under one header and so > their GL codes will be following each other and bring presentable > arrangement. (accounts in the same header, their GL codes should have > relation) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-389) Arrange the accounts that fall under one account type in order of their GL codes
[ https://issues.apache.org/jira/browse/FINERACT-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947542#comment-15947542 ] Thisura commented on FINERACT-389: -- [~santoshmath] PR sent at https://github.com/openMF/community-app/pull/2157 Please review and merge. > Arrange the accounts that fall under one account type in order of their GL > codes > > > Key: FINERACT-389 > URL: https://issues.apache.org/jira/browse/FINERACT-389 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: p2 > > Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2825 > Original Description: > Accounts in chart of accounts are arranged by their account type but those > accounts in the specific account type are randomly arranged. > I was recommending for the accounts in the same account type to be arranged > by their GL code. Since the relating accounts will be under one header and so > their GL codes will be following each other and bring presentable > arrangement. (accounts in the same header, their GL codes should have > relation) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FINERACT-389) Arrange the accounts that fall under one account type in order of their GL codes
[ https://issues.apache.org/jira/browse/FINERACT-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946422#comment-15946422 ] Thisura commented on FINERACT-389: -- I am working on this. > Arrange the accounts that fall under one account type in order of their GL > codes > > > Key: FINERACT-389 > URL: https://issues.apache.org/jira/browse/FINERACT-389 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: p2 > > Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2825 > Original Description: > Accounts in chart of accounts are arranged by their account type but those > accounts in the specific account type are randomly arranged. > I was recommending for the accounts in the same account type to be arranged > by their GL code. Since the relating accounts will be under one header and so > their GL codes will be following each other and bring presentable > arrangement. (accounts in the same header, their GL codes should have > relation) -- This message was sent by Atlassian JIRA (v6.3.15#6346)