0020856: Module cannot add working Translation tab to different module

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0020856

Openbravo ERP

E. Translation

public

2012-06-25 13:45

2022-02-01 08:09

Reporter

CZDave

Assigned To

Triage Platform Base

Priority

normal

Severity

minor

Reproducibility

always

Status

acknowledged

Resolution

open

Platform

OS Version

7 x64

Product Version

3.0MP10.1

Target Version

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Web browser

Mozilla Firefox

Modules

Core

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0020856: Module cannot add working Translation tab to different module

Description

When 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 Reproduce

For 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 Solution

Generally 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.

Additional Information