Community
Participate
Working Groups
The report I designed gets its data from a select statement which joins two tables. After moving one column from one relation to the other the report generation didn't work. The error message in the report told me that there was a "Malformed input at byte xyz" while creating a hierarchy:XYZ.NewTabularHierarchy. In the end I found the cause of this behaviour: BIRT saves the input columns of the resultset along with their positions. After moving one column to another table its position changed, but this was not reflected in the design. After adjusting the positions (they appear twice in the document) the report worked again. There are several problems I think: - The error message was misleading. A malformed input at byte xyz, thrown by a method with "utf" in its name lead me to the wrong track at first - Why are the positions necessary in the report design? There are names defined, why not use them? - If the positions are necessary: They should be available in the report designer. I didn't find them somewhere but had to dig in the xml file.
Moving one column from table1 to table2,if table2 has the column bingding with the same name,the operation can be done and report can work normally.If table2 hasn't the same name column bingding,the operation is invalid and an error message like "The column binding for the data "report.Body[1].Detail[0].Cells[0].Content[0]" with column name "CUSTOMERNUMBER" is not defined." will pop up. But I don't see message like "Malformed input at byte xyz". Could you provide more detail information about how to reproduce it or a sample report I can test with?
Hello, I'm not clear about the reproduce description "moving one column from one relation to the other", I tried to change condition order for the join query but no issue found. Could you provide more detail information about it?
