Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0018628Openbravo ERP00. Application dictionarypublic2011-09-27 18:072011-10-18 17:26
Reporteregoitz 
Assigned Tomarvintm 
PriorityhighSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version3.0MP2 
Target Version3.0MP5Fixed in Version3.0MP5 
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
Summary0018628: Having many datasets on a module, the order is not caculated when they are have elements related.
DescriptionHaving many datasets on a module, the order is not caculated when they are have elements related.
Steps To Reproduce-Create a new module
-Define new partners and categories
-Define a new dataset for partners
-Define a new dataset for partner categories
-Export both datastes
-export and package the module
-Install on another server
-Apply all the datasets.
*sometimes you get an error depending on id of the datasets.
if the id of the dataset of the partner is smaller than the categories if fails because the partner refernces to a category that does not exist.
Proposed Solution*Add a new column seqno on the dataset
*Order with this new column the dataset when applying.
Additional Information
TagsNo tags attached.
Relationships
depends on backport 00186292.50MP35 closed marvintm Having many datasets on a module, the order is not caculated when they are have elements related. 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-09-27 18:07egoitzNew Issue
2011-09-27 18:07egoitzAssigned To => marvintm
2011-09-27 18:07egoitzModules => Core
2011-09-27 18:09egoitzResolution time => 1322521200
2011-09-27 18:09egoitzStatusnew => scheduled
2011-09-27 18:09egoitzfix_in_branch => pi
2011-09-27 18:10egoitzversion3.0MP2 => 2.50MP32
2011-09-27 18:10egoitzTarget Version3.0MP5 => 2.50MP35
2011-09-27 18:10egoitzfix_in_branchpi =>
2011-09-27 18:10egoitzversion2.50MP32 => 3.0MP2
2011-09-27 18:10egoitzTarget Version2.50MP35 => 3.0MP5
2011-10-14 11:19hgbotCheckin
2011-10-14 11:19hgbotNote Added: 0041830
2011-10-14 11:19hgbotStatusscheduled => resolved
2011-10-14 11:19hgbotResolutionopen => fixed
2011-10-14 11:19hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/d936e4752dc960281669059afda5f1c87804f5db [^]
2011-10-14 15:35dbazStatusresolved => closed
2011-10-14 15:35dbazFixed in Version => 3.0MP5
2011-10-18 17:26hudsonbotCheckin
2011-10-18 17:26hudsonbotNote Added: 0041905

Notes
(0041830)
hgbot   
2011-10-14 11:19   
Repository: erp/devel/pi
Changeset: d936e4752dc960281669059afda5f1c87804f5db
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Fri Oct 14 11:16:01 2011 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/d936e4752dc960281669059afda5f1c87804f5db [^]

Fixed issue 18628. Added a column used to order datasets inside a module.

---
M src-db/database/model/tables/AD_DATASET.xml
M src-db/database/sourcedata/AD_COLUMN.xml
M src-db/database/sourcedata/AD_FIELD.xml
M src/org/openbravo/erpCommon/ad_forms/UpdateReferenceData_data.xsql
M src/org/openbravo/erpCommon/modules/ModuleReferenceDataOrgTree_data.xsql
---
(0041905)
hudsonbot   
2011-10-18 17:26   
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/3a0e09f510aa [^]

Maturity status: Test