Community
Participate
Working Groups
Build Identifier: 20100218-1602 If a dataset column name contains a backslash (for example "MY\COLUMN") and is used in a chart value series, there are 2 problems: - You must replace MY\COLUMN with MY\\COLUMN to fix the error about a binding which does not exist. - Then, the chart is displayed correctly in the preview, but not in the final report which is empty. Reproducible: Always
(In reply to comment #0) > Build Identifier: 20100218-1602 > > If a dataset column name contains a backslash (for example "MY\COLUMN") and is > used in a chart value series, there are 2 problems: > - You must replace MY\COLUMN with MY\\COLUMN to fix the error about a binding > which does not exist. > - Then, the chart is displayed correctly in the preview, but not in the final > report which is empty. > > Reproducible: Always For reproduce purpose, which database were you using that allows the backslash in column name? I tried with scriptdataset and no matter I use \ or \\, chart preview dialog contains error. Is that possible you could attach a report design that use scriptdatasource or flatfile that can reproduce the case(2): >Then, the chart is displayed correctly in the preview, but not in the final report which is empty.
Which BIRT build were you using? I can only reproduce the issue #1 in release BIRT 2.6.0 release build. Further more, in 2.6.0 release build, you can not create x-axis group even after change the column name to use "\\". But this issue has been resolved in latest 2.6.1 (v20100819-0630)
This had been fixed in the latest check-ins. The cause is some special characters in binding name/column name don't be added backslash to ensure the string expression correct.
Verified in daily build 2.6.2.v20101210
