[
https://issues.apache.org/jira/browse/OFBIZ-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16788596#comment-16788596 ]
Pierre Smits commented on OFBIZ-10846:
--------------------------------------
So, wrong gl transactions have been generated since forever and it's not a bug, rather a feature that just needed some minor improvement?
> In AddFinAccountTrans selectable glAccountId values are sorted on glAccountId
> -----------------------------------------------------------------------------
>
> Key: OFBIZ-10846
> URL:
https://issues.apache.org/jira/browse/OFBIZ-10846> Project: OFBiz
> Issue Type: Improvement
> Components: accounting
> Affects Versions: Trunk
> Reporter: Pierre Smits
> Assignee: Suraj Khurana
> Priority: Major
> Attachments: OFBIZ-10846.patch
>
>
> In the AddFinAccountTrans form in FinAccountForms.xml the values in the field glAccountId are sorted on the primary key, per
> {code:java}
> <field name="glAccountId" title="${uiLabelMap.GlAccount}">
> <drop-down>
> <entity-options entity-name="GlAccountOrganizationAndClass" key-field-name="glAccountId" description="${accountCode} - ${accountName} [${glAccountId}]">
> <entity-constraint name="organizationPartyId" operator="equals" env-name="defaultOrganizationPartyId"/>
> <entity-order-by field-name="glAccountId"/>
> </entity-options>
> </drop-down>
> </field>
> {code}
> The sort order should however be on the accountCode field of the entity
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Locked
