|View Issue Details[ Jump to Notes ]||[ Issue History ] [ Print ]|
|Type||Category||Severity||Reproducibility||Date Submitted||Last Update|
|backport||[Openbravo ERP] 09. Financial management||major||always||2015-11-17 13:32||2015-11-18 14:03|
|Priority||immediate||Resolution||fixed||Fixed in Version|
|Status||closed||Fix in branch||Fixed in SCM revision||d816f0fd4dd9|
|OS||Linux 64 bit||Database||PostgreSQL||Java version||1.6.0_18|
|OS Version||Professional Appliance||Database version||8.3.9||Ant version||1.7.1|
|Product Version||SCM revision|
|Review Assigned To||vmromanos|
|Regression level||Packaging and release|
|Regression introduced in release||pi|
|Regression introduced by commit||https://code.openbravo.com/erp/devel/pi/rev/fe7e7c17712b [^]|
|Triggers an Emergency Pack||No|
0031517: Empty matched document when running Match Statement pocess
|Description||Matched Document keeps empty in Match Statement grid although record is matched.|
|Steps To Reproduce||As FB Admin:|
- Go to Financial Account windonw and select Cuenta de Banco
Move to Imported Bank Statements tab and create a record.
Move to Bank Statement Lines tab and create a record with payment in = 10.
Click on Process button.
- Click on Match Statement button.
Click Cancel in Confirm popup.
Select the record shown in the grid and click + button (Add new transaction).
Select any gl item in Add Transaction popup and click Done.
Clear filter is necessary to show matched bank statements.
Realize record appears as matched but Matched Document column is empty.
|Tags||No tags attached.|
|Relationships [ Relation Graph ] [ Dependency Graph ]|
Author: Alvaro Ferraz <alvaro.ferraz <at> openbravo.com>
Date: Tue Nov 17 18:13:59 2015 +0100
URL: http://code.openbravo.com/erp/backports/3.0PR15Q3.4/rev/d816f0fd4dd9296a4c2f280b0c652df5e67fa28c [^]
Fixes issue 31517: Empty matched document in Match Statement
The problem was that two new columns were added in aprm_matchstatement hql query in the middle of the select clause, while they were added as two new columns at the end of ad_column. As the columns order was not the same between the hql query and the ad_column and some columns did not have an alias in hql query and some others did not have an entity alias in ad_column, some column values were lost.
To fix it, we added an alias to all columns in aprm_matchstatement hql query (matchedDocument had no alias) and an entity alias to all ad_columns in aprm_matchstatement table (Transaction, bslUpdated and matchedDocument columns had no entity alias and Affinity column had a wrong entity alias).
With this, all columns of aprm_matchstatement will be correctly filled with their values in Match Statement grid.
If new columns are added to the hql query, they can go in any order in the select clause and in the ad_column, but they will need to have both an alias in the hql query and an entity alias in the ad_column, following this documentation: http://wiki.openbravo.com/wiki/How_to_create_a_HQL_Based_Table#Column_Definition [^]
|Code review + testing OK|
|2015-11-17 15:29||aferraz||Type||defect => backport|
|2015-11-17 15:29||aferraz||Target Version||3.0PR16Q1 => 3.0PR15Q3.4|
|2015-11-18 14:01||hgbot||Note Added: 0081950|
|2015-11-18 14:01||hgbot||Status||scheduled => resolved|
|2015-11-18 14:01||hgbot||Resolution||open => fixed|
|2015-11-18 14:01||hgbot||Fixed in SCM revision||=> http://code.openbravo.com/erp/backports/3.0PR15Q3.4/rev/d816f0fd4dd9296a4c2f280b0c652df5e67fa28c [^]|
|2015-11-18 14:03||vmromanos||Review Assigned To||=> vmromanos|
|2015-11-18 14:03||vmromanos||Note Added: 0081952|
|2015-11-18 14:03||vmromanos||Status||resolved => closed|
|Copyright © 2000 - 2009 MantisBT Group|