Issue 99116 - RPT: cannot open report in bug doc anymore
Summary: RPT: cannot open report in bug doc anymore
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Base
Classification: Application
Component: ReportBuilder (show other issues)
Version: DEV300m40
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: OOo 3.2
Assignee: ocke.janssen
QA Contact: issues@dba
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2009-02-11 12:34 UTC by Frank Schönheit
Modified: 2009-03-10 10:59 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
document to reproduce the bug case (21.79 KB, application/vnd.sun.xml.base)
2009-02-11 12:37 UTC, Frank Schönheit
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Frank Schönheit 2009-02-11 12:34:05 UTC
- open the attached database document
- open the contained report by double-clicking it
=> an error message pops up saying "The document ... could not be opened".

Pressing the "more" button brings you to a dialog saying something about a
WrappedTargetException in SOReportJobFactory.execute.

A part of the problem is already described in issue 99110: The table which the
chart is based on contains numeric values in a VARCHAR column. Obviously, this
confuses the report generator so it generates somehow invalid documents. For
text documents, this results in an invalid chart, for spreadsheet documents (in
the attached bug doc, the report is set up to create a spreadsheet doc), it
results in the report not generated at all.

Why I separate this as separate issue is the following:
In m39, the report in the bug doc can be opened, it "only" displays wrong data
in the chart. However, in CWS rptfix04, the report cannot be opened anymore.
Comment 1 Frank Schönheit 2009-02-11 12:35:37 UTC
fs->oj: Please investigate the severity of this issue. As said, it seems that it
has been introduced in CWS rptfix04. Given the lateness of this CWS, I would
agree to *not* fixing it there, but only if the error condition is rare enough
so that chances for users to trigger/encounter it are low.
Comment 2 Frank Schönheit 2009-02-11 12:37:52 UTC
Created attachment 60089 [details]
document to reproduce the bug case
Comment 3 Frank Schönheit 2009-02-11 14:07:19 UTC
okay, I built a m40 version containing the fix for issue 98549. The bug occurs
there, too, so it is not a regression in rptfix04, but a regression between m39
and m40.
Comment 4 Frank Schönheit 2009-02-11 14:08:42 UTC
targeting to 3.2 for the moment. Whether or not this is 3.1-worth depends on the
root cause, and how easy users can encounter the problem.

fs->oj: Please have a look at the cause for this issue, so we can make an
educated decision about the target.
Comment 5 ocke.janssen 2009-03-10 10:58:04 UTC
Works in a OOO310_m4
Comment 6 ocke.janssen 2009-03-10 10:59:35 UTC
Closing