Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0008745Openbravo ERPJ. Demo datapublic2009-04-23 14:022011-01-15 00:00
Reportermtaal 
Assigned Togorkaion 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionout of date 
PlatformOS5OS Version
Product Versionpi 
Target VersionpiFixed 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
Summary0008745: Project data in Small Bazaar sample data: tree node values in ad_treenode for tree PR point to non-existing projects
DescriptionIn Small Bazaar sample data the AD_TreeNode table for the project tree contains values which are incorrect, there are no projects for those ids. See message below (ignore the treenode id as it differs for SmallBazaar).

0 [main] ERROR org.openbravo.dal.xml.EntityXMLConverter - TreeNode: The value 1000002 used in treeNode 52118BF1A8614D84E040007F01005FEC is not valid, there is no Project with that id
3 [main] ERROR org.openbravo.dal.xml.EntityXMLConverter - TreeNode: The value 1000003 used in treeNode 52118BF1A8624D84E040007F01005FEC is not valid, there is no Project with that id
4 [main] ERROR org.openbravo.dal.xml.EntityXMLConverter - TreeNode: The value 1000007 used in treeNode 52118BF1A8664D84E040007F01005FEC is not valid, there is no Project with that id
5 [main] ERROR org.openbravo.dal.xml.EntityXMLConverter - TreeNode: The value 1000008 used in treeNode 52118BF1A8674D84E040007F01005FEC is not valid, there is no Project with that id
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
has duplicate defect 0009400pi closed rafaroda Fails to export sample data 
has duplicate defect 0010610 closed rafaroda Ant export.sample.data 
related to defect 0011161 closed gorkaion export.sample.data for Accounting test client has data for ad_treenode pointing to non-existing records in FinancialMgmtElementV 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-04-23 14:02mtaalNew Issue
2009-04-23 14:02mtaalAssigned To => rafaroda
2009-04-23 14:02mtaalOBNetwork customer => No
2009-04-23 14:02mtaalRegression testing => No
2009-04-27 11:30rajagopalNote Added: 0015761
2009-04-27 11:34rajagopalNote Edited: 0015761
2009-04-28 13:29psarobeNote Added: 0015848
2009-04-28 13:29psarobeStatusnew => feedback
2009-04-28 13:33mtaalNote Added: 0015849
2009-04-28 13:33mtaalNote Added: 0015850
2009-04-29 16:53psarobeSeveritymajor => minor
2009-04-29 16:53psarobeStatusfeedback => scheduled
2009-05-17 11:08mtaalNote Added: 0016406
2009-05-17 11:14mtaalNote Added: 0016407
2009-06-01 17:18rafarodaAssigned Torafaroda => gorkaion
2009-06-01 17:18rafarodaCategory08. Project and service management => J. Demo data
2009-06-09 17:00rafarodaRelationship addedhas duplicate 0009400
2009-09-18 13:04rafarodaRelationship addedhas duplicate 0010610
2009-10-28 14:22shuehnerRelationship addedrelated to 0011161
2011-01-14 10:45gorkaionNote Added: 0033642
2011-01-14 10:45gorkaionStatusscheduled => closed
2011-01-14 10:45gorkaionResolutionopen => out of date
2011-01-15 00:00anonymoussf_bug_id0 => 3158555

Notes
(0015761)
rajagopal   
2009-04-27 11:30   
(edited on: 2009-04-27 11:34)
Below is the link of ant task execution log while executing ant export.sample.data for defect id : 8276.

http://pastebin.com/f14b36978 [^]
(0015848)
psarobe   
2009-04-28 13:29   
Hi Martin,

Which is the consequence of this? Shall we fix it for 250MP1?

Thanks
(0015849)
mtaal   
2009-04-28 13:33   
Hi Rafa,
Maybe one thing which can be checked if in 2.40 this 'error' already existed (so treenodes which point to non-existing projects). It would be good to have this extra info (to determine if this error started in 2.50).

In any case I don't think that we need to solve this in MP1. It is just sample.data and it can be solved also as part of a fix later.

gr. Martin
(0015850)
mtaal   
2009-04-28 13:33   
I mean 'Hi Pablo' ofcourse :-)

gr. Martin
(0016406)
mtaal   
2009-05-17 11:08   
Hi Pablo, Rafa,
I tried export.sample.data and it did not work because of this issue. I can disable the check for this for now to make exporting possible. But I think it makes sense to solve this for MP2.

The solution is two step:
1) validate that it is correct that the refered projects are not there, if they should have been there then that shows a different issue (projects not part of sample data...)
2) if these projects are indeed not ment to be part of sample data then these tree nodes can be removed, if the tree that contains these nodes does not have any other nodes then this tree can also be removed.

Imo both steps should be done by someone responsible for the project management functionality.

Here is the previous log string this time with the id's of the treenode:
TreeNode (with id:52118BF1A8614D84E040007F01005FEC): The value 1000002 used in treeNode 52118BF1A8614D84E040007F01005FEC is not valid, there is no Project with that id
TreeNode (with id:52118BF1A8624D84E040007F01005FEC): The value 1000003 used in treeNode 52118BF1A8624D84E040007F01005FEC is not valid, there is no Project with that id
TreeNode (with id:52118BF1A8664D84E040007F01005FEC): The value 1000007 used in treeNode 52118BF1A8664D84E040007F01005FEC is not valid, there is no Project with that id
TreeNode (with id:52118BF1A8674D84E040007F01005FEC): The value 1000008 used in treeNode 52118BF1A8674D84E040007F01005FEC is not valid, there is no Project with that id

gr. Martin
(0016407)
mtaal   
2009-05-17 11:14   
Correction :-), the data is exported, still it makes sense to solve this imo. It is little work and solves an inconsistency in the data

gr. Martin
(0033642)
gorkaion   
2011-01-14 10:45   
SmallBazaar sample data has been replaced by F&B