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

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] E. Translationminoralways2012-06-25 13:452022-02-01 08:09
ReporterCZDaveView Statuspublic 
Assigned ToTriage Platform Base 
PrioritynormalResolutionopenFixed in Version
StatusacknowledgedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSWindowsDatabasePostgreSQLJava version1.6.0 Update 24
OS Version7 x64Database version8.4.11Ant version1.7.1
Product Version3.0MP10.1SCM revision 
Review Assigned To
Web browserMozilla Firefox
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0020856: Module cannot add working Translation tab to different module

DescriptionWhen creating a Translation tab for client data, associated translation DB table must have the exact same name as original data table with the _TRL suffix. However a module can't create a table with the same prefix as another module's table, so their names will always differ in prefix and the translation table is not recognized, giving a warning in generate.entities.quick build task, eg:
WARN org.openbravo.base.model.Property - M_Product_Category.Name is not translatable: null translationProperty
Steps To ReproduceFor example, trying to add a Translation tab to Product Category:

1. Create a module with DB prefix ATRL
2. Create a template including that module
3. Create a table in database similar to M_PRODUCT_TRL named ATRL_PRODUCT_CATEGORY_TRL, with standard columns and: M_PRODUCT_CATEGORY_ID, AD_LANGUAGE, NAME, DOCUMENTNOTE, ISTRANSLATED (with foreign keys and constraints)
4. Register this table in Tables and Columns window
5. Create a new tab named Translation for the Product Category window and set its Translation tab property
6. Set the Translation property of the column Name for M_PRODUCT_CATEGORY tab

When running ant smartbuild you'll get a warning:
WARN org.openbravo.base.model.Property - M_Product_Category.Name is not translatable: null translationProperty
and although you can create translations, they won't be displayed anywhere when switching to different language
Proposed SolutionGenerally there could be a field for Table in Tables and Columns to select which table it translates and DAL should take this into account.
Or at least all meaningful tables in Core should contain the Translation tab.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
has duplicate design defect 0013055 closedalostale it is not posible create a new translation tab 

-  Notes
AugustoMauch (manager)
2012-09-24 12:34

Effort: 10
Impact: mid
Plan: mid

- Issue History
Date Modified Username Field Change
2012-06-25 13:45 CZDave New Issue
2012-06-25 13:45 CZDave Assigned To => alostale
2012-06-25 13:45 CZDave Web browser => Mozilla Firefox
2012-06-25 13:45 CZDave Modules => Core
2012-09-10 15:08 alostale Relationship added has duplicate 0013055
2012-09-24 12:34 AugustoMauch Web browser Mozilla Firefox => Mozilla Firefox
2012-09-24 12:34 AugustoMauch Note Added: 0052321
2012-09-24 12:34 AugustoMauch Status new => scheduled
2017-03-31 14:36 alostale Status scheduled => acknowledged
2017-04-10 14:33 alostale Assigned To alostale => platform
2022-02-01 08:09 alostale Assigned To platform => Triage Platform Base

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker