Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0025744Openbravo ERPA. Platformpublic2014-02-17 10:022014-09-02 09:28
Reporterjecharri 
Assigned ToAugustoMauch 
PriorityurgentSeveritymajorReproducibilityalways
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browserGoogle Chrome
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0025744: Problems during the rebuild
DescriptionProblems during the rebuild.

The problems happens when you have 2 tables with same name but different databse prefix doing reference to same table
Steps To Reproduce-create 2 tables --> "sn_table_inv" and "sl_table_inv"
-two tables should have a foreign key to same table. For example "c_bpartner" table

Execute "ant smartbuild -Dlocal=no" command and you will get similar error to:

     [java] 0 [main] INFO org.openbravo.base.model.ModelProvider - Building runtime model
     [java] 12158 [main] ERROR org.openbravo.base.model.NamingUtil - ERROR: Property name computation fails for property BusinessPartner.null using new name tableInvCustomerList there is more then one property with the same name, being robust and renaming property automatically. If this error appears during update.database then this is possibly solved automatically. Otherwise this should be repaired manually by changing the AD_Column.name of the column C_BPartner.null

Above error will create a BusinessPartner entity with 2 similar properties:
-PROPERTY_TABLEINVCUSTOMERLIST
-PROPERTY_TABLEINVCUSTOMERLIST185

Due to that, the developer could have problems if he or she was using method getTableInvCustomerList.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-02-17 10:02jecharriNew Issue
2014-02-17 10:02jecharriAssigned To => AugustoMauch
2014-02-17 10:02jecharriWeb browser => Google Chrome
2014-02-17 10:02jecharriModules => Core
2014-02-17 10:02jecharriResolution time => 1395270000
2014-02-17 10:02jecharriTriggers an Emergency Pack => No
2014-02-17 10:04AugustoMauchWeb browserGoogle Chrome => Google Chrome
2014-02-17 10:04AugustoMauchDescription Updatedbug_revision_view_page.php?rev_id=5454#r5454
2014-02-17 10:04jecharriWeb browserGoogle Chrome => Google Chrome
2014-02-17 10:04jecharriDescription Updatedbug_revision_view_page.php?rev_id=5455#r5455
2014-02-17 10:04jecharriSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=5457#r5457
2014-02-24 12:01shankarbAssigned ToAugustoMauch => shankarb
2014-03-03 16:55alostaleNote Added: 0064740
2014-03-03 16:57alostaleWeb browserGoogle Chrome => Google Chrome
2014-03-03 16:57alostaleNote Added: 0064741
2014-03-03 16:57alostaleTypedefect => design defect
2014-03-03 16:57alostaleWeb browserGoogle Chrome => Google Chrome
2014-03-03 16:57alostaleResolution time1395270000 =>
2014-03-03 16:57alostaleTarget Version3.0MP32 =>
2014-09-02 09:28shankarbAssigned Toshankarb => AugustoMauch

Notes
(0064740)
alostale   
2014-03-03 16:55   
This happens in case the modules delivering the tables have DBPrefix with length 1 or 2 (see https://code.openbravo.com/erp/devel/pi/file/fbadcf337117/src/org/openbravo/base/model/NamingUtil.java#l327 [^])
(0064741)
alostale   
2014-03-03 16:57   
Moving to design defect: fixing it requires to keep old names (PROPERTY_TABLEINVCUSTOMERLIST185) together with new ones in order to maintain API.