If you have a custom requirement, create a derived form and override
the field.
-David
On Jun 28, 2009, at 10:53 PM, Ashish Vijaywargiya wrote:
Thanks a lot guys for your comments.
Please see my comments inline:
--
Ashish Vijaywargiya
David E Jones wrote:
That's a good point Jacopo. It seems like in a lot of places the
account code has more meaning than the account name since the
account code often implies the accounts place in the hierarchy of
accounts, there can be subtle differences between accounts that are
not well represented in the names, and just like we do with things
like Jira issue numbers once you refer to it a few times it is
easier to remember the code than it is to remember the name.
I agree from you David but most of the time when you do search you
tries to find by containing "String" either in subject or in whole
content of description instead of searching the jira issue number.
IMO you can remember the jira issue number when it was popular in
the community due to some long discussion going on it or it has been
created by yourself.
I guess the most important point for a drop-down is seeing the
accounts in their normal order, with hierarchy and all, which is
what you get when sorted by the accountCode.
Anyway, +1 for changing it back... or perhaps not exactly back but
to something like:
${accountCode}-${accountName} [${glAccountId}]
What should be the case suppose I have 100 Char of Accounts and I
have few accounts that has parent - child relationship. For example:
I have a Gl Account which has 35 child account. The account codes
are something like: 700001, 700002 ............... So for this I
will start typing four numbers and then press down arrow key for
navigating to particular account to which I am trying to find.
Instead of this if I will be having option to search by letter then
I can easily reach to my Gl account with lesstyping.
If we talk about the remembering of "Numbers" & "String" then the
best example is to remember domain name instead of IP address. In
India most of the Accountant work by remembering name instead of
Account Code or GlAccountId.
What can be the best way to deal this thing? Here are the few points
that are coming to my mind:
1) Define the order as suggested by David (${accountCode}-$
{accountName} [${glAccountId}]) in a property file as the default
one and then create a service that return a map and this values can
be fetched from that map in the form fields. Also define the order-
by field in the property file and handle this in the service.
2) Write my custom code and change the drop down values as per my
requirements. But I would not prefer to go in this way. Because
maintenance of code will be difficult for me in future if any
changes comes to those screens.
I will wait for your feedback on this and then will proceed
accordingly.
and remove both entity-order-by elements that are there now, and
add one for "accountCode". The reason for this is that currently
glAccountId is always the same as accountCode for the OOTB
GlAccounts, but that may not always be the case for people and in
fact the point of having an accountCode that is not a primary key
is so that it can be changed over time.
-David
On Jun 28, 2009, at 8:51 AM, Jacopo Cappellato wrote:
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, [email protected] 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
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
=
=
=
=
=
=
=
=
=
=
=
===================================================================
--- ofbiz/trunk/applications/accounting/widget/
GlobalGlAccountsForms.xml (original)
+++ ofbiz/trunk/applications/accounting/widget/
GlobalGlAccountsForms.xml Sun Jun 28 08:37:58 2009
@@ -132,7 +132,8 @@
</field>
<field name="parentGlAccountId">
<drop-down allow-empty="true">
- <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}">
+ <entity-order-by field-name="accountName"/>
<entity-order-by field-name="glAccountId"/>
</entity-options>
</drop-down>
