Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014173Openbravo ERPA. Platformpublic2010-08-12 19:332010-08-18 10:57
Reporterrafaroda 
Assigned Tomtaal 
PriorityimmediateSeveritymajorReproducibilityalways
StatusclosedResolutionunable to reproduce 
PlatformOS20OS VersionCommunity Appliance
Product Version2.50MP20 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0014173: Can't export module developed in Spanish: INCORRECT_CLIENT_ORG_PROPERTY_NAME
DescriptionI can't export a module developed in Spanish.

[validateModules] +++++++++++++++++++++++++++++++++++++++++++++++++++
[validateModules] Errors for Validation type: INCORRECT_CLIENT_ORG_PROPERTY_NAME
[validateModules] +++++++++++++++++++++++++++++++++++++++++++++++++++
[validateModules] Table EVEBUCO_OBJECTIVE has a column referencing AD_Client. The AD_Column.name (note: different from AD_Column.columnname!) of this column should have the value client, it currently has entidad
[validateModules] Table EVEBUCO_OBJECTIVE has a column referencing AD_Org. The AD_Column.name (note: different from AD_Column.columnname!) of this column should have the value organization, it currently has organizacin
Steps To ReproduceHaving installed the Spanish Translation module http://forge.openbravo.com/projects/languagemodulespanish/module [^]

0) Create a new module with language Spanish (Spain) selected [0]
1) Develop a new window for this module [1]. Don't forget to Synchronize Terminology!
2) ant export.database

[0] http://wiki.openbravo.com/wiki/ERP/2.50/Developers_Guide/How_To_Create_and_Package_a_Module [^]
[1] http://wiki.openbravo.com/wiki/ERP/2.50/Developers_Guide/How_to_develop_a_new_window [^]
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to design defect 0014190 acknowledged Triage Platform Base Can't export module developed with non-Western base language 
related to defect 0014172 closed marvintm Missleading warning info when packaging module: NOT_PART_OF_FOREIGN_KEY 
Attached Files? OBJECTIVE.java (5,661) 2010-08-16 00:11
https://issues.openbravo.com/file_download.php?file_id=2865&type=bug
? RESET_COLUMN_NAMES.sql (959) 2010-08-18 10:57
https://issues.openbravo.com/file_download.php?file_id=2879&type=bug
Issue History
Date ModifiedUsernameFieldChange
2010-08-12 19:33rafarodaNew Issue
2010-08-12 19:33rafarodaAssigned To => alostale
2010-08-12 19:33rafarodaRelationship addedrelated to 0014172
2010-08-12 19:34rafarodaIssue Monitored: rafaroda
2010-08-15 22:57rafarodaSeverityminor => critical
2010-08-15 22:57rafarodaSummaryMissleading warning info when packaging module: INCORRECT_CLIENT_ORG_PROPERTY_NAME => Can't export module developed in Spanish: INCORRECT_CLIENT_ORG_PROPERTY_NAME
2010-08-15 22:57rafarodaDescription Updatedbug_revision_view_page.php?rev_id=676#r676
2010-08-15 22:57rafarodaSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=678#r678
2010-08-15 23:21rafarodaRelationship addedrelated to 0014190
2010-08-15 23:22rafarodaNote Added: 0029967
2010-08-16 00:11rafarodaFile Added: OBJECTIVE.java
2010-08-16 00:11rafarodaNote Added: 0029970
2010-08-16 08:05alostaleAssigned Toalostale => mtaal
2010-08-16 08:05alostaleStatusnew => scheduled
2010-08-16 08:46mtaalNote Added: 0029976
2010-08-16 08:46mtaalStatusscheduled => feedback
2010-08-16 09:46rafarodaNote Added: 0029979
2010-08-16 09:50networkbStatusfeedback => new
2010-08-16 11:06rafarodaNote Edited: 0029979bug_revision_view_page.php?bugnote_id=0029979#r682
2010-08-17 09:51rafarodaNote Added: 0030043
2010-08-17 11:08rafarodaPrioritynormal => immediate
2010-08-17 11:08rafarodaSeveritycritical => major
2010-08-17 11:09rafarodaNote Edited: 0029979bug_revision_view_page.php?bugnote_id=0029979#r689
2010-08-17 13:57rafarodaNote Added: 0030069
2010-08-17 13:57rafarodaStatusnew => feedback
2010-08-17 13:59mtaalNote Added: 0030070
2010-08-17 18:42rafarodaStatusfeedback => new
2010-08-17 18:48rafarodaNote Added: 0030087
2010-08-17 18:48rafarodaStatusnew => closed
2010-08-17 18:48rafarodaResolutionopen => unable to reproduce
2010-08-18 00:00anonymoussf_bug_id0 => 3047309
2010-08-18 10:57rafarodaNote Added: 0030106
2010-08-18 10:57rafarodaFile Added: RESET_COLUMN_NAMES.sql

Notes
(0029967)
rafaroda   
2010-08-15 23:22   
Any language can be used as a base for a module http://wiki.openbravo.com/wiki/ERP/2.50/Developers_Guide/Concepts/Multi-Language_and_Translations#Module.27s_language [^]

See also related issue 0014190 Can't export module developed with non-Western base language
(0029970)
rafaroda   
2010-08-16 00:11   
Please notice that the code generated in src-gen for a module with base language Spanish is in the form (see file OBJECTIVE.java attached):
* public static final String PROPERTY_ENTIDAD = "entidad";
* public static final String PROPERTY_ORGANIZACIN = "organizacin"; (notice that รณ has been skipped)
* public void setEntidad(Client entidad) {
        set(PROPERTY_ENTIDAD, entidad);
    }
* public Organization getOrganizacin() {
        return (Organization) get(PROPERTY_ORGANIZACIN);
    }
* public void setDescripcin(String descripcin) {
        set(PROPERTY_DESCRIPCIN, descripcin);
    }
* public void setCreadoPor(User creadoPor) {
        set(PROPERTY_CREADOPOR, creadoPor);
    }
(0029976)
mtaal   
2010-08-16 08:46   
As far as I can see this is not an error. The message is clear afaics.

Why can't the column.name be changed to respectively client and organization?

gr. Martin
(0029979)
rafaroda   
2010-08-16 09:46   
(edited on: 2010-08-17 11:09)
Hi Martin,

Column.name is changed automatically to "entidad" and "organizacin" by the Synchronize Terminology process when:
1) Spanish translation module is installed.
2) And module base language is Spanish.

I can change back those column.name to "client" and "organization", but they will be changed again to "entidad" and "organizacin" when I run Synchronize Terminology, so I suspect that there is something wrong here (maybe with entities generation and export database validations since Synchronize Terminology seems OK to me).

Thanks for your answer.
(0030043)
rafaroda   
2010-08-17 09:51   
Good morning Martin,

Is this issue acknowledge as a bug?

Thanks.
(0030069)
rafaroda   
2010-08-17 13:57   
Martin,

I'm making some more test to try to reproduce it consistently (seems not to be happening always). I put this issue in feedback.

Sorry for the inconveniences.
(0030070)
mtaal   
2010-08-17 13:59   
Yes I asked Asier because afaics the sync terminology should not change the ad_column.name.
But Asier has not yet answered.

gr. Martin
(0030087)
rafaroda   
2010-08-17 18:48   
Hi Martin,

I proceed with the closing of this issue. I've not been able to reproduce it again.

Somehow a Synchronize Terminology in my development environment set all column names in Spanish but starting from 0 I was not able to make it fail again.

Sorry for the inconveniences.
(0030106)
rafaroda   
2010-08-18 10:57   
If someone else suffers for this strange issue, I reset my column names with the PL/SQL "RESET_COLUMN_NAMES" attached.