Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014218Openbravo ERPB. User interfacepublic2010-08-17 13:242010-09-19 00:00
Reporternetworkb 
Assigned Toiperdomo 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionsuspended 
PlatformOS20OS VersionCommunity Appliance
Product Version2.50MP20 
Target Version2.50MP22Fixed in Version 
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
Summary0014218: error to add a chart of type XY dataset in jasper report
Description. when you add a new chart of type XY dataset in a report jrxml, error is returned:
    
Error:
Index: -1, Size: 1
Steps To Reproduce. open a report jrxml with ireport 3.0.0
. add a chart of type XY dataset:
   . go to Edit -> insert element -> tree map:
         select Barra XY
         . go to properties-> edit char properties -> data -> detail -> add :
              X expresion: new BigDecimal("4")
              Y expresion: new BigDecimal("8")

. compile and run the report
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to design defect 0014609 acknowledged Triage Platform Base Error when using a XY dataset in a jasper report 
Attached Files? ReportCashJR.jrxml (33,224) 2010-08-17 13:36
https://issues.openbravo.com/file_download.php?file_id=2878&type=bug
log exception.log (4,352) 2010-08-30 16:59
https://issues.openbravo.com/file_download.php?file_id=2985&type=bug
? org.openbravo.examples.report.graph-0.0.1.obx (9,273) 2010-08-31 11:37
https://issues.openbravo.com/file_download.php?file_id=2997&type=bug
? org.openbravo.examples.report.graph-0.0.1bis.obx (50,621) 2010-09-13 12:11
https://issues.openbravo.com/file_download.php?file_id=3070&type=bug
Issue History
Date ModifiedUsernameFieldChange
2010-08-17 13:24networkbNew Issue
2010-08-17 13:24networkbAssigned To => dbaz
2010-08-17 13:27dbazAssigned Todbaz => alostale
2010-08-17 13:36networkbFile Added: ReportCashJR.jrxml
2010-08-30 08:52alostaleStatusnew => scheduled
2010-08-30 08:52alostaleAssigned Toalostale => iperdomo
2010-08-30 08:52alostalefix_in_branch => pi
2010-08-30 16:59iperdomoFile Added: exception.log
2010-08-30 17:00iperdomoNote Added: 0030471
2010-08-30 17:00iperdomoStatusscheduled => feedback
2010-08-31 11:37iperdomoFile Added: org.openbravo.examples.report.graph-0.0.1.obx
2010-08-31 11:37iperdomoNote Added: 0030524
2010-09-13 10:53networkbNote Added: 0030974
2010-09-13 12:11networkbFile Added: org.openbravo.examples.report.graph-0.0.1bis.obx
2010-09-13 12:12networkbNote Added: 0030981
2010-09-13 16:25networkbStatusfeedback => new
2010-09-13 16:25networkbfix_in_branchpi =>
2010-09-13 16:25networkbDescription Updatedbug_revision_view_page.php?rev_id=835#r835
2010-09-18 09:56iciordiaNote Added: 0031203
2010-09-18 09:56iciordiaStatusnew => closed
2010-09-18 09:56iciordiaResolutionopen => suspended
2010-09-18 10:00iciordiaRelationship addedrelated to 0014609
2010-09-19 00:00anonymoussf_bug_id0 => 3070577

Notes
(0030471)
iperdomo   
2010-08-30 17:00   
Please provide a 'real' example, Adding dummy values to a chart makes no sense.
Remember that charts in HTML reports are not supported.

You'll see in the exception that the error comes from the jasper library.
(0030524)
iperdomo   
2010-08-31 11:37   
Please try the attached module, you'll see that with real data from the report's query the issue is not reproducible.

Test the module and close the issue.

Cheers,

Iván
(0030974)
networkb   
2010-09-13 10:53   
We can't reproduce the problem with your report

the bug can be closed.

thanks
(0030981)
networkb   
2010-09-13 12:12   
sorry, my last comunication was not correct.

the problem is the same with the graphic type "barra XY" (XY dataset).
In the obx, the selected graphic is "category dataset".

I have attached a new obx with the graphic "XY dataset"
(0031203)
iciordia   
2010-09-18 09:56   
The issue has been solved by using a different dataset (XYZ dataset). It is pending to research why the XY dataset is not working, see reported issue 14609

Ismael