Dear Telerik Support Team,
I am reaching out to request technical assistance regarding the implementation of a "Terms and Conditions" section that should function as a completely independent additional page at the end of my report.
Current Report Structure: My main report includes Page Header, Detail, and Page Footer (containing total calculations) sections.
Current Configuration (Attempted without success): To force the legal text into an independent final page, I have configured the following:
Special Request: I have attached my report definition file (.trdp). Could you please review my current structure and modify the attached report using the most robust configuration to solve this behavior?
I am reaching out to request technical assistance regarding the implementation of a "Terms and Conditions" section that should function as a completely independent additional page at the end of my report.
Current Report Structure: My main report includes Page Header, Detail, and Page Footer (containing total calculations) sections.
Current Configuration (Attempted without success): To force the legal text into an independent final page, I have configured the following:
- Section used: ReportFooterSection to contain the legal text.
- PageBreak Property: Set to Before.
- Text Component: HtmlTextBox with CanGrow set to True.
- KeepTogether Property: I have tested both True and False settings.
- Section Merging: The long text starts rendering immediately after the Details section on the main page, ignoring the page break or fragmenting erratically.
- Page Footer Conflict: The Page Footer elements (invoice totals and page numbers) from the main invoice continue to print on the pages where the legal text appears, causing visual overlaps.
- What is the cleanest way to add this final page? Given the standard report flow, how can I insert this block so it "breaks" the flow and takes over a full page without inheriting the layout (Header/Footer) of the previous pages?
- Conditional Visibility Control: How do you recommend hiding the Page Header and Page Footer specifically on these final "Terms" pages?
- Report Architecture: For text that spans one or more full pages, is it better to continue using the ReportFooterSection, or would you recommend using a SubReport or a Group Footer without a grouping expression?
Special Request: I have attached my report definition file (.trdp). Could you please review my current structure and modify the attached report using the most robust configuration to solve this behavior?