Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0043603Openbravo ERPE. Translationpublic2020-03-27 22:242020-04-08 23:21
lbressan 
inigo_lerga 
normalminoralways
scheduledopen 
5
3.0PR19Q3.2 
 
Google Chrome
Core
No
0043603: Journal Entries Report not showing the traslation from account tree
When the Account tree have elements value translation, the translations are not fetched into the Journal Entries Report with the languaje profile that the user selects. The ReportGeneralLedgerJournal_data.xsql does not query from c_elementvalue_trl table.
1.- Go to Account Tree Window and select any account.
2.- Select any element in the Element value tab.
3.- Create a record in "Translation" Tab for any language (e.i. Spanish) and check the traslation checkbox. (See image 1)
4.- Change the profile languaje to Spanish (See image 2)
5.- Execute the Journal entries report (See image 3)
No tags attached.
png 1.png (71,350) 2020-03-27 22:24
https://issues.openbravo.com/file_download.php?file_id=14221&type=bug
png

png 2.png (89,810) 2020-03-27 22:25
https://issues.openbravo.com/file_download.php?file_id=14222&type=bug
png

png 3.png (76,436) 2020-03-27 22:26
https://issues.openbravo.com/file_download.php?file_id=14223&type=bug
png

diff 43603-join.diff (5,075) 2020-04-03 11:44
https://issues.openbravo.com/file_download.php?file_id=14263&type=bug
Issue History
2020-03-27 22:24lbressanNew Issue
2020-03-27 22:24lbressanAssigned To => platform
2020-03-27 22:24lbressanFile Added: 1.png
2020-03-27 22:24lbressanWeb browser => Google Chrome
2020-03-27 22:24lbressanModules => Core
2020-03-27 22:24lbressanResolution time => 1588284000
2020-03-27 22:24lbressanTriggers an Emergency Pack => No
2020-03-27 22:25lbressanFile Added: 2.png
2020-03-27 22:26lbressanFile Added: 3.png
2020-03-30 06:53alostaleAssigned Toplatform => Triage Finance
2020-03-30 08:13Alberto_SolaIssue Monitored: Alberto_Sola
2020-03-30 12:03inigo_lergaAssigned ToTriage Finance => inigo_lerga
2020-03-30 12:03inigo_lergaStatusnew => scheduled
2020-03-30 15:21lbressanNote Added: 0118876
2020-04-02 10:22inigo_lergaNote Added: 0118916
2020-04-03 11:41dmiguelezWeb browserGoogle Chrome => Google Chrome
2020-04-03 11:41dmiguelezSeveritymajor => minor
2020-04-03 11:44dmiguelezNote Added: 0118935
2020-04-03 11:44dmiguelezFile Added: 43603-join.diff
2020-04-08 09:48dmiguelezWeb browserGoogle Chrome => Google Chrome
2020-04-08 09:48dmiguelezResolution time1588284000 =>
2020-04-08 09:48dmiguelezTypedefect => design defect
2020-04-08 23:21eugeniIssue Monitored: eugeni

Notes
(0118876)
lbressan   
2020-03-30 15:21   
The problem affects any screen that displays or searches ledger accounts, for example, daily ledgers, balance sheets.
(0118916)
inigo_lerga   
2020-04-02 10:22   
--Test Plan Mantis--
As the System Administrator role:
  - Go to the Language window. Open the "Spanish (Spain)"
    record and enable the System Language checkbox.
    Save the record.

Log out and Log in.
As the F&B International Group Admin role and Spanish as
Profile's language:
  - Go to the Account Tree window. Select the "F&B International
    Group Account Account" record.
  - Go to the Element Value Tab and search for the "Inventory Asset"
    record and select it.
  - Go to the Translation Subtab and open the Spanish(Spain) record.
    Put any desired name and enable the Translation checkbox.
    Save the record.
  - Go to the Journal Entries Report window. Select "F&B EspaƱa, S.A" as
    Organization and "F&B International Group US/A/US Dollar" as General Ledger.
    Press the Search button.

  #In this moment the previously translation appears instead of Inventory Asset#
(0118935)
dmiguelez   
2020-04-03 11:44   
The severity of this issue has been updated to minor following the Bug Reporting Guidelines:
http://wiki.openbravo.com/wiki/Bug_Reporting_Guidelines [^]

Also, answering the previous comment, reviewing all accounting reports can not be reported as an Issue, since it is a Design Defect that requires analysis of every report, one by one.

Finally, as for the solution of this issue, a proposed patch is attached. However, performance must be tested in any client before applying this patch in production. The query of this report can retrieve plenty of data and is prone to have performance issues if not tested properly