Hello, Staff!
I created report which consists of 3 subreports.
Each subreport have more than 100 records and the height of subreport is calculating incorrect. Part of data is cut.
When I set the height of html element manually (using Developer Toolbar or FireBug) I see hidden part of data.
Is it an issue of Telerik reports?
Also why the subreport placed on one page on preview? Is it the software limitation?
Thanks!
I created report which consists of 3 subreports.
Each subreport have more than 100 records and the height of subreport is calculating incorrect. Part of data is cut.
When I set the height of html element manually (using Developer Toolbar or FireBug) I see hidden part of data.
Is it an issue of Telerik reports?
Also why the subreport placed on one page on preview? Is it the software limitation?
Thanks!
6 Answers, 1 is accepted
0
Hello Alex,
Please provide more information on your exact setup - are you using TextBox or HtmlTextBox items to display the text? Additionally have you altered the CanGrow and TextWrap properties which are True by default?
We see from your download history that you're using an older version of the product - please try upgrading to see if the problem persists.
As for your second inquiry - this is expected behavior of the HTML rendering, explained in details in the Design Considerations for HTML Rendering, namely: "Due to the fact that HTML is not a page oriented format, report sections cannot be split and therefore KeepTogether property is ignored (always set to true) in HTML Rendering."
In other words, all items placed in a single report section would be rendered in a single page in the web report viewer.
All the best,
Steve
the Telerik team
Please provide more information on your exact setup - are you using TextBox or HtmlTextBox items to display the text? Additionally have you altered the CanGrow and TextWrap properties which are True by default?
We see from your download history that you're using an older version of the product - please try upgrading to see if the problem persists.
As for your second inquiry - this is expected behavior of the HTML rendering, explained in details in the Design Considerations for HTML Rendering, namely: "Due to the fact that HTML is not a page oriented format, report sections cannot be split and therefore KeepTogether property is ignored (always set to true) in HTML Rendering."
In other words, all items placed in a single report section would be rendered in a single page in the web report viewer.
All the best,
Steve
the Telerik team
0

Alex
Top achievements
Rank 1
answered on 14 Dec 2010, 11:40 AM
Hello, Steve!
Thanks for your reply.
My report too simple (just by example):
MainReport has Header and Detail section.
Header has only one TextBox with Value - "Header" :)
Detail section has 2 subreport, nothing else.
Each subreport has group header, detail and group footer.
Detail section has 2 HtmlTextBoxes (I try to use TextBox - the same result):
Subreport NeedDataSource handler is simple too:
On Preview I got the following report (Picture 1)
As you can see group footer is absent and the latest record on report is #96 but should be #99 (group 50 it's data from subreport2)
I use the Developer ToolBar to resize html element and voilà : Picture 2 (after resize)
Thanks, Alex
Thanks for your reply.
My report too simple (just by example):
MainReport has Header and Detail section.
Header has only one TextBox with Value - "Header" :)
Detail section has 2 subreport, nothing else.
Each subreport has group header, detail and group footer.
Detail section has 2 HtmlTextBoxes (I try to use TextBox - the same result):
Subreport NeedDataSource handler is simple too:
var list =
new
List<DataTestClass>();
for
(
int
i = 0; i < 100; i++)
{list.Add(
new
DataTestClass() {Group = i / 10, Number = i, Value =
"Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum"
});
}
(sender
as
Telerik.Reporting.Processing.Report).DataSource = list;
On Preview I got the following report (Picture 1)
As you can see group footer is absent and the latest record on report is #96 but should be #99 (group 50 it's data from subreport2)
I use the Developer ToolBar to resize html element and voilà : Picture 2 (after resize)
Thanks, Alex
0

Alex
Top achievements
Rank 1
answered on 14 Dec 2010, 11:43 AM
Hello, Steve!
If you need I can upload test application.
Regards, Alex
If you need I can upload test application.
Regards, Alex
0
Hi Alex,
Can you please upgrade to the latest official version Q3 2010 and if the problem persists, we would then appreciate if you open a support ticket and provide us with a sample.
Best wishes,
Steve
the Telerik team
Can you please upgrade to the latest official version Q3 2010 and if the problem persists, we would then appreciate if you open a support ticket and provide us with a sample.
Best wishes,
Steve
the Telerik team
0

Alex
Top achievements
Rank 1
answered on 15 Dec 2010, 12:18 PM
Hi Steve!
I downloaded and installed Q3 and I noticed that line cut issue fixed.
But looks like another problem appear:
NeedDataSource not fired for second subreport.
I downloaded and installed Q3 and I noticed that line cut issue fixed.
But looks like another problem appear:
NeedDataSource not fired for second subreport.
0
Hi Alex,
Do you use the same report instance as ReportSource for both subreport items? If that is the case either assign a new report instance to the second subreport item or upgrade to the latest internal build (available in your account) where this shortcoming should be fixed as well.
Best wishes,
Steve
the Telerik team
Do you use the same report instance as ReportSource for both subreport items? If that is the case either assign a new report instance to the second subreport item or upgrade to the latest internal build (available in your account) where this shortcoming should be fixed as well.
Best wishes,
Steve
the Telerik team