Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0018629
TypeCategorySeverityReproducibilityDate SubmittedLast Update
backport[Openbravo ERP] 00. Application dictionaryminoralways2011-09-27 18:072011-10-14 15:35
ReporteregoitzView Statuspublic 
Assigned Tomarvintm 
PriorityhighResolutionfixedFixed in Version2.50MP35
StatusclosedFix in branch2.50Fixed in SCM revisionb426d2c20640
ProjectionnoneETAnoneTarget Version2.50MP35
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product Version2.50MP33SCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0018629: 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.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
blocks defect 00186283.0MP5 closedmarvintm Having many datasets on a module, the order is not caculated when they are have elements related. 

-  Notes
(0041774)
hgbot (developer)
2011-10-12 17:19

Repository: erp/stable/2.50
Changeset: b426d2c20640c5389ef3b039563e04447a5affb7
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Wed Oct 12 17:18:48 2011 +0200
URL: http://code.openbravo.com/erp/stable/2.50/rev/b426d2c20640c5389ef3b039563e04447a5affb7 [^]

Fixed issue 18629. 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
---
(0041775)
hgbot (developer)
2011-10-12 18:16

Repository: erp/stable/2.50
Changeset: e53e34b8390a2f77c3c254a15d2ec13434dd9f8b
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Wed Oct 12 18:15:26 2011 +0200
URL: http://code.openbravo.com/erp/stable/2.50/rev/e53e34b8390a2f77c3c254a15d2ec13434dd9f8b [^]

Related to issue 18629. Fixed wrong default. Improved SQL order.

---
M src-db/database/sourcedata/AD_COLUMN.xml
M src/org/openbravo/erpCommon/ad_forms/UpdateReferenceData_data.xsql
---

- Issue History
Date Modified Username Field Change
2011-09-27 18:09 egoitz Type defect => backport
2011-09-27 18:09 egoitz fix_in_branch => 2.50
2011-09-27 18:11 egoitz version 3.0MP2 => 2.50MP33
2011-09-27 18:11 egoitz Target Version 3.0MP5 => 2.50MP35
2011-10-12 17:19 hgbot Checkin
2011-10-12 17:19 hgbot Note Added: 0041774
2011-10-12 17:19 hgbot Status scheduled => resolved
2011-10-12 17:19 hgbot Resolution open => fixed
2011-10-12 17:19 hgbot Fixed in SCM revision => http://code.openbravo.com/erp/stable/2.50/rev/b426d2c20640c5389ef3b039563e04447a5affb7 [^]
2011-10-12 18:16 hgbot Checkin
2011-10-12 18:16 hgbot Note Added: 0041775
2011-10-14 15:35 dbaz Status resolved => closed
2011-10-14 15:35 dbaz Fixed in Version => 2.50MP35


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker