Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0018116Openbravo ERP00. Application dictionarypublic2011-07-28 17:152011-08-06 05:33
Reporteradrianromero 
Assigned Tomarvintm 
PriorityurgentSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS20OS Version
Product Versionpi 
Target Version3.0MP2Fixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0018116: The process that creates fields in a table based on a database table does not name properly fields
DescriptionTaking a new created table in the database with the following fields:

AD_ORG_ID
AD_CLIENT_ID
CREATED
CREATEDBY
UPDATED
UPDATEDBY
ISACTIVE

Some of these columns are named incorrectly and the window created using this table does now work properly until all columns are properly named. The correct names for these columns are:

Organization
Client
Creation Date
Created By
Updated
Updated By
Active
Steps To Reproduce* Create a new table in the database with the fields listed in the Description.
* As System Administrator, create a new table in Openbravo for the database table created.
* Execute the process "Create Columns from DB" and verify the columns created.
* Create a new Window, Tab and fields for the new table created, and a menu option.
* Generate the entitys and as Administrator open the window and try to save. Verify that the record cannot be saved and errors appear.
* Change the name of the columns according to the description. Regenerate the entity and verify that now the window works and records can be saved, deleted, etc.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0011528 closed marvintm Export validation fails after table creation 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-07-28 17:15adrianromeroNew Issue
2011-07-28 17:15adrianromeroAssigned To => iperdomo
2011-07-28 17:15adrianromeroModules => Core
2011-07-28 17:15adrianromeroOBNetwork customer => No
2011-08-01 11:39psarobePrioritynormal => urgent
2011-08-01 11:39psarobeStatusnew => scheduled
2011-08-01 11:49psarobeAssigned Toiperdomo => marvintm
2011-08-01 11:50psarobeRelationship addedrelated to 0011528
2011-08-01 12:13psarobeTarget Version3.0MP3 => 3.0MP2
2011-08-01 17:13hgbotCheckin
2011-08-01 17:13hgbotNote Added: 0039748
2011-08-01 17:13hgbotStatusscheduled => resolved
2011-08-01 17:13hgbotResolutionopen => fixed
2011-08-01 17:13hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/0951c9cfecef7cdd3cf59b4f79cfff5b4f842bfa [^]
2011-08-04 18:07hgbotCheckin
2011-08-04 18:07hgbotNote Added: 0039876
2011-08-05 11:18shuehnerNote Added: 0039891
2011-08-05 11:18shuehnerStatusresolved => closed
2011-08-06 05:32hudsonbotCheckin
2011-08-06 05:32hudsonbotNote Added: 0039926
2011-08-06 05:33hudsonbotCheckin
2011-08-06 05:33hudsonbotNote Added: 0039970

Notes
(0039748)
hgbot   
2011-08-01 17:13   
Repository: erp/devel/pi
Changeset: 0951c9cfecef7cdd3cf59b4f79cfff5b4f842bfa
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Mon Aug 01 17:04:08 2011 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/0951c9cfecef7cdd3cf59b4f79cfff5b4f842bfa [^]

Fixed issue 18116. Names of common columns will now be generated correctly

---
M src-db/database/model/functions/AD_TABLE_IMPORT.xml
---
(0039876)
hgbot   
2011-08-04 18:07   
Repository: erp/devel/pi
Changeset: 7f7af04a2913f34fe7cb22d753c215ddfa875432
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Thu Aug 04 18:06:49 2011 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/7f7af04a2913f34fe7cb22d753c215ddfa875432 [^]

Related to issue 18116. Restored wrongly changed part of sql query

---
M src-db/database/model/functions/AD_TABLE_IMPORT.xml
---
(0039891)
shuehner   
2011-08-05 11:18   
Reviewed/test on pi/pgsql (rev-id: 7f7af04a2913). process now creates column with correct name (which is != columnname) so dal naming conventions are directly fine (tested with defining tab ontop of newly created table). Verified that existing 'table is missing common column' error message is still working correct. Running process on oracle also works without error and created the ad_column entries with the correct names.
(0039926)
hudsonbot   
2011-08-06 05:32   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/5744448753e7 [^]

Maturity status: Test
(0039970)
hudsonbot   
2011-08-06 05:33   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/5744448753e7 [^]

Maturity status: Test