Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0015130Openbravo ERP09. Financial managementpublic2010-11-08 17:172011-01-27 19:10
Reporterxabiermerino 
Assigned Todalsasua 
PriorityhighSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version2.50MP23 
Target Version2.50MP26Fixed in Version2.50MP26 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0015130: Bad behaviour in the Account Tree || Element >> Element Value if you change data in the Account Combination
DescriptionIf you change the name of an account in Account Tree || Element >> Element Value, the description (value + name) of Account Combination is not updated until you save.
Steps To Reproduce- AS Openbravo Admin fo to Financial Management || Accounting || Setup || Account Tree || Element >> Element Value
- Select the account 99909
- Change the name and save.
- Go to Financial Management || Accounting || Setup || Account Combination
- Select the account 99909.
- Realize that the description has not been updated.
- Introduce an space in the alias. Now you can use the 'Record button'
- Save
- Realize that the description has been updated
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 00148892.50MP24 closed harikrishnan Organization filter does not work properly in general ledger report 
related to defect 00148492.40MP13 closed adrianromero Error when modifying element value which is referenced from more than one accounting combination, in Oracle 
depends on defect 0015605 closed adrianromero Bad behaviour in the Account Tree || Element >> Element Value if you change data in the Account Combination 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-11-08 17:17xabiermerinoNew Issue
2010-11-08 17:17xabiermerinoAssigned To => dalsasua
2010-11-08 17:17xabiermerinoIssue Monitored: networkb
2010-11-08 17:19dalsasuaAssigned Todalsasua => adrianromero
2010-11-08 17:36adrianromeroRelationship addedrelated to 0014889
2010-11-10 16:55adrianromeroRelationship addedrelated to 0014849
2010-11-25 11:41adrianromeroNote Added: 0032841
2010-11-25 13:32adrianromeroStatusnew => feedback
2011-01-11 12:44adrianromeroStatusfeedback => scheduled
2011-01-11 12:44adrianromerofix_in_branch => pi
2011-01-11 12:45adrianromeroTypedefect => backport
2011-01-11 12:45adrianromerofix_in_branchpi =>
2011-01-11 12:45adrianromeroIssue cloned0015605
2011-01-11 12:45adrianromeroRelationship addeddepends on 0015605
2011-01-12 11:24dalsasuaAssigned Toadrianromero => dalsasua
2011-01-12 16:20dalsasuafix_in_branch => 2.50
2011-01-12 16:29hgbotCheckin
2011-01-12 16:29hgbotNote Added: 0033599
2011-01-12 16:29hgbotStatusscheduled => resolved
2011-01-12 16:29hgbotResolutionopen => fixed
2011-01-12 16:29hgbotFixed in SCM revision => http://code.openbravo.com/erp/stable/2.50/rev/f546e05e2e7864d1c7463867e9813c58fc16c224 [^]
2011-01-27 19:10dalsasuaStatusresolved => closed
2011-01-27 19:10dalsasuaFixed in Version => 2.50MP26

Notes
(0032841)
adrianromero   
2010-11-25 11:41   
There is needed to be disused whether this value has to be calculated in a callout or in the trigger.
(0033599)
hgbot   
2011-01-12 16:29   
Repository: erp/stable/2.50
Changeset: f546e05e2e7864d1c7463867e9813c58fc16c224
Author: David Alsasua <david.alsasua <at> openbravo.com>
Date: Wed Jan 12 16:28:27 2011 +0100
URL: http://code.openbravo.com/erp/stable/2.50/rev/f546e05e2e7864d1c7463867e9813c58fc16c224 [^]

Fixes issue 15130: Bad behaviour in the Account Tree || Element
There existed one inconsistency: element value trigger was using account description to build the valid combination description, while valid combination trigger was using the name of the account, to build the description of the combination.
The correct approach is to use the account name

---
M src-db/database/model/triggers/C_ELEMENTVALUE_TRG.xml
---