Re: svn commit: r789074 - /ofbiz/trunk/applications/accounting/widget/GlobalGlAccountsForms.xml

[Jacopo Cappellato]

Are we sure that this is the best way to go? Usually chart of accounts are prepared using special conventions for account id (i.e. "accountCode"); see for example how the demo data is organized. I think it is important to keep that order; also, most of the time, accountants already know the account codes and use them instead of the descriptions.

Thoughts?

Jacopo

On Jun 28, 2009, at 2:37 AM, ash...@apache.org wrote:

Author: ashish
Date: Sun Jun 28 08:37:58 2009
New Revision: 789074

URL: http://svn.apache.org/viewvc?rev=789074&view=rev
Log:
Trying to make Accountant life easy.
Its easy to find general ledger from alphabet instead of number.

Modified:
 ofbiz/trunk/applications/accounting/widget/GlobalGlAccountsForms.xml


URL: 
http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/widget/GlobalGlAccountsForms.xml?rev=789074&r1=789073&r2=789074&view=diff

@@ -132,7 +132,8 @@
      </field>
      <field name="parentGlAccountId">
          <drop-down allow-empty="true">

+                    <entity-order-by field-name="accountName"/>
                  <entity-order-by field-name="glAccountId"/>
              </entity-options>
          </drop-down>

Modified: ofbiz/trunk/applications/accounting/widget/ GlobalGlAccountsForms.xml = = = = = = = = ====================================================================== --- ofbiz/trunk/applications/accounting/widget/ GlobalGlAccountsForms.xml (original) +++ ofbiz/trunk/applications/accounting/widget/ GlobalGlAccountsForms.xml Sun Jun 28 08:37:58 2009 - <entity-options key-field-name="glAccountId" entity- name="GlAccount" description="[${glAccountId}] ${accountName}-$ {accountCode}"> + <entity-options key-field-name="glAccountId" entity- name="GlAccount" description="${accountName} [${glAccountId}]-$ {accountCode}">

smime.p7s
Description: S/MIME cryptographic signature