Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
backport[Openbravo ERP] 09. Financial managementmajoralways2015-11-17 13:322015-11-18 14:03
ReporteraferrazView Statuspublic 
Assigned Toaferraz 
PriorityimmediateResolutionfixedFixed in Version
StatusclosedFix in branchFixed in SCM revisiond816f0fd4dd9
ProjectionnoneETAnoneTarget Version3.0PR15Q3.4
OSLinux 64 bitDatabasePostgreSQLJava version1.6.0_18
OS VersionProfessional ApplianceDatabase version8.3.9Ant version1.7.1
Product VersionSCM revision 
Review Assigned Tovmromanos
Web browser
Regression levelPackaging and release
Regression date2015-11-11
Regression introduced in releasepi
Regression introduced by commit [^]
Triggers an Emergency PackNo

0031517: Empty matched document when running Match Statement pocess

DescriptionMatched Document keeps empty in Match Statement grid although record is matched.
Steps To ReproduceAs 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.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
blocks defect 00315153.0PR16Q1 closedaferraz Empty matched document when running Match Statement pocess 

-  Notes
hgbot (developer)
2015-11-18 14:01

Repository: erp/backports/3.0PR15Q3.4
Changeset: d816f0fd4dd9296a4c2f280b0c652df5e67fa28c
Author: Alvaro Ferraz <alvaro.ferraz <at>>
Date: Tue Nov 17 18:13:59 2015 +0100
URL: [^]

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: [^]

M modules/org.openbravo.advpaymentmngt/src-db/database/sourcedata/AD_COLUMN.xml
M modules/org.openbravo.advpaymentmngt/src-db/database/sourcedata/AD_TABLE.xml
vmromanos (manager)
2015-11-18 14:03

Code review + testing OK

- Issue History
Date Modified Username Field Change
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 Checkin
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 => [^]
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
Powered by Mantis Bugtracker