| Linking chart by parameter causes error when a NULL param value is reached [message #57968] |
Wed, 13 July 2005 23:48  |
Eclipse User |
|
|
|
Originally posted by: none.none.none
I have a chart embedded in a group and linked by a single parameter
(datatype is string). This group is actually a subgroup of one or more
groups. So there may not always be data for the group, and thus no
parameter value for the chart.
When this happens (when there is no data for the group), I get this error
message:
There are errors on the report page:
- There are error(s) in Chart:null
Error0 : data.engine.NullDefaultInParamValue(1 time)detail: Default value
for
input parameter cannot be null.Error1 : Error.ExtendedItemRenderingError(1
time)detail: There are problems(s) rendering Chart extended item .The
DataSet
bound to the chart returned no rows.
I think this would be a common/expected occurence that should not raise an
error, but rather the query should just be skipped.I entered this into
bugzilla and it looks like they classified it as an "enhancement" and a
target release of 2.0. This surprises me a bit since many of my reports
have big ugly error messages in them and they shouldn't be there... I mean,
a report shouldn't throw an error due to no-data.
This is really killing some reports, does anyone know of a workaround to
hold me over?? I'm out of ideas, except for maybe modifying the viewer code
to suppress errors, which I'd rather not do.
Thanks!
|
|
|
| Re: Linking chart by parameter causes error when a NULL param value is reached [message #58188 is a reply to message #57968] |
Thu, 14 July 2005 04:15  |
| Eclipse User |
|
|
|
Originally posted by: none.none.com
Hi Chris,
The bugzilla entry has been resolved.
Thanks,
David
"chris" <none@none.none> wrote in message
news:db4n9n$3p5$1@news.eclipse.org...
>I have a chart embedded in a group and linked by a single parameter
>(datatype is string). This group is actually a subgroup of one or more
>groups. So there may not always be data for the group, and thus no
>parameter value for the chart.
> When this happens (when there is no data for the group), I get this error
> message:
>
> There are errors on the report page:
> - There are error(s) in Chart:null
> Error0 : data.engine.NullDefaultInParamValue(1 time)detail: Default value
> for
> input parameter cannot be null.Error1 : Error.ExtendedItemRenderingError(1
> time)detail: There are problems(s) rendering Chart extended item .The
> DataSet
> bound to the chart returned no rows.
>
> I think this would be a common/expected occurence that should not raise an
> error, but rather the query should just be skipped.I entered this into
> bugzilla and it looks like they classified it as an "enhancement" and a
> target release of 2.0. This surprises me a bit since many of my reports
> have big ugly error messages in them and they shouldn't be there... I
> mean, a report shouldn't throw an error due to no-data.
>
> This is really killing some reports, does anyone know of a workaround to
> hold me over?? I'm out of ideas, except for maybe modifying the viewer
> code to suppress errors, which I'd rather not do.
>
> Thanks!
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.07080 seconds
Home