0014173: Can't export module developed in Spanish: INCORRECT_CLIENT_ORG_PROPERTY_NAME

(0029967)
rafaroda (developer)
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 (developer)
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 (manager)
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 (developer)
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 (developer)
2010-08-17 09:51

Good morning Martin,

Is this issue acknowledge as a bug?

Thanks.

(0030069)
rafaroda (developer)
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 (manager)
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 (developer)
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 (developer)
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.

Issue History
Date Modified	Username	Field	Change
2010-08-12 19:33	rafaroda	New Issue
2010-08-12 19:33	rafaroda	Assigned To	=> alostale
2010-08-12 19:33	rafaroda	Relationship added	related to 0014172
2010-08-12 19:34	rafaroda	Issue Monitored: rafaroda
2010-08-15 22:57	rafaroda	Severity	minor => critical
2010-08-15 22:57	rafaroda	Summary	Missleading 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:57	rafaroda	Description Updated	View Revisions
2010-08-15 22:57	rafaroda	Steps to Reproduce Updated	View Revisions
2010-08-15 23:21	rafaroda	Relationship added	related to 0014190
2010-08-15 23:22	rafaroda	Note Added: 0029967
2010-08-16 00:11	rafaroda	File Added: OBJECTIVE.java
2010-08-16 00:11	rafaroda	Note Added: 0029970
2010-08-16 08:05	alostale	Assigned To	alostale => mtaal
2010-08-16 08:05	alostale	Status	new => scheduled
2010-08-16 08:46	mtaal	Note Added: 0029976
2010-08-16 08:46	mtaal	Status	scheduled => feedback
2010-08-16 09:46	rafaroda	Note Added: 0029979
2010-08-16 09:50	networkb	Status	feedback => new
2010-08-16 11:06	rafaroda	Note Edited: 0029979	View Revisions
2010-08-17 09:51	rafaroda	Note Added: 0030043
2010-08-17 11:08	rafaroda	Priority	normal => immediate
2010-08-17 11:08	rafaroda	Severity	critical => major
2010-08-17 11:09	rafaroda	Note Edited: 0029979	View Revisions
2010-08-17 13:57	rafaroda	Note Added: 0030069
2010-08-17 13:57	rafaroda	Status	new => feedback
2010-08-17 13:59	mtaal	Note Added: 0030070
2010-08-17 18:42	rafaroda	Status	feedback => new
2010-08-17 18:48	rafaroda	Note Added: 0030087
2010-08-17 18:48	rafaroda	Status	new => closed
2010-08-17 18:48	rafaroda	Resolution	open => unable to reproduce
2010-08-18 00:00	anonymous	sf_bug_id	0 => 3047309
2010-08-18 10:57	rafaroda	Note Added: 0030106
2010-08-18 10:57	rafaroda	File Added: RESET_COLUMN_NAMES.sql

Notes
(0029967) rafaroda (developer) 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 (developer) 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 (manager) 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 (developer) 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 (developer) 2010-08-17 09:51	Good morning Martin, Is this issue acknowledge as a bug? Thanks.

(0030069) rafaroda (developer) 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 (manager) 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 (developer) 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 (developer) 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.