Update word-rendering-design-considerations.md (#1472)
* Update word-rendering-design-considerations.md * Update excel-rendering-design-considerations.md * Update error-handling-in-reports-and-report-viewers.md * Update reportsource-model-binding.md * Update excel-rendering-design-considerations.md * Update word-rendering-design-considerations.md --------- Co-authored-by: Momchil Zanev <108741271+mzanev@users.noreply.github.com>
This commit is contained in:
Todor Arabadzhiev
GitHub
Родитель
69c95e1d48
Коммит
f766b3dcb6
|
|
@ -13,7 +13,7 @@ previous_url: /mvc-report-viewer-reportsource-model-binding
|
|||
|
||||
The HTML5 Report Viewer comes with an MVC wrapper that does the JavaScript configuration of the report viewer, where you can type the initial settings of the viewer in `C#` or `VB.NET`. The settings include `Id`, `ServiceUrl`, `templateUrl`, client-side `ReportSource`, and more - [HTML5 Report Viewer Initialization]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/api-reference/report-viewer-initialization%}).
|
||||
|
||||
> It is important to know that the MVC project appears as a client for the Reporting RESt Service serving the HTML5 Viewer, even if the service is in the same project. The HTML5 Viewer and Reporting REST Service operates in a client-server model that is not related to the MVC architecture of the project. Modifications in reports and run-time data-bindings can be performed only by the Reporting REST Service, on the server where the Reporting REST Service is running. For more details, check [REST Service Report Source Resolver]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/rest-service-report-source-resolver/overview%}).
|
||||
> It is important to know that the MVC project appears as a client for the Reporting REST Service serving the HTML5 Viewer, even if the service is in the same project. The HTML5 Viewer and Reporting REST Service operates in a client-server model that is not related to the MVC architecture of the project. Modifications in reports and run-time data-bindings can be performed only by the Reporting REST Service, on the server where the Reporting REST Service is running. For more details, check [REST Service Report Source Resolver]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/rest-service-report-source-resolver/overview%}).
|
||||
|
||||
## Getting started
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Error Handling in Reports and Report Viewers
|
||||
description: "Learn how to handle errors occuring during the report document generation and errors related to Report Viewers and the ReportProcessor class used for processing Telerik reports."
|
||||
description: "Learn how to handle errors occurring during the report document generation and errors related to Report Viewers and the ReportProcessor class used for processing Telerik reports."
|
||||
type: how-to
|
||||
page_title: Handle errors in Telerik Reporting
|
||||
slug: error-handling-in-reports-and-report-viewers
|
||||
|
|
@ -22,7 +22,7 @@ res_type: kb
|
|||
|
||||
## Description
|
||||
|
||||
Reports and Report Viewers are created in such manner that errors may not result in system failure, but the end user can still see an error message. It is a common requirement to make these error messages more user-friendly and comprehensive for users.
|
||||
Reports and Report Viewers are created in such a manner that errors may not result in system failure, but the end user can still see an error message. It is a common requirement to make these error messages more user-friendly and comprehensive for users.
|
||||
|
||||
Telerik Reporting provides mechanisms for custom handling errors, where you can add logic and UI that you want to appear in such cases.
|
||||
|
||||
|
|
@ -30,17 +30,17 @@ Telerik Reporting provides mechanisms for custom handling errors, where you can
|
|||
|
||||
1. **Errors related to processing items, which do not lead to breaking the report document's generation**.
|
||||
|
||||
* If these errors are not handled, the report will be processed and rendered, but there might be **red error messages** in the report at the place of the items which failed being processed.
|
||||
* Such errors can be caught in the [report's Error event](/api/telerik.reporting.erroreventhandler). If a report is created as a **TRDX|TRDP** file, you can [deserialize]({%slug telerikreporting/using-reports-in-applications/program-the-report-definition/serialize-report-definition-in-xml%}#deserialize-report-definition-from-xml-file)|[unpackage]({%slug telerikreporting/using-reports-in-applications/program-the-report-definition/package-report-definition%}#unpackaging)the file and subscribe the report instance to its Error event.
|
||||
* If these errors are not handled, the report will be processed and rendered, but there might be **red error messages** in the report in the place of the items that failed to be processed.
|
||||
* Such errors can be caught in the [report's Error event](/api/telerik.reporting.erroreventhandler). If a report is created as a **TRDX** | **TRDP** file, you can [deserialize]({%slug telerikreporting/using-reports-in-applications/program-the-report-definition/serialize-report-definition-in-xml%}#deserialize-report-definition-from-xml-file) | [unpackage]({%slug telerikreporting/using-reports-in-applications/program-the-report-definition/package-report-definition%}#unpackaging)the file and subscribe the report instance to its Error event.
|
||||
|
||||
The report's Error event has information about the processing element throwing the exception (`sender`), and provides arguments allowing you to read the exception and cancel the further processing. If you throw a custom exception in the Error event, the further processing will be stopped, and if you use a Report Viewer, you will receive the custom error message in the viewer's preview.
|
||||
The report's Error event has information about the processing element throwing the exception (`sender`) and provides arguments allowing you to read the exception and cancel the further processing. If you throw a custom exception in the Error event, further processing will be stopped, and if you use a Report Viewer, you will receive the custom error message in the viewer's preview.
|
||||
|
||||
2. **Errors related to processing items, breaking the report document's generation**.
|
||||
|
||||
* If these errors are not handled, the report will not be further processed. If you use a Report Viewer, and error will be displayed in viewer's preview.
|
||||
* If these errors are not handled, the report will not be further processed. If you use a Report Viewer, an error will be displayed in the viewer's preview.
|
||||
* Such errors can be caught through the instance processing the report such as a [Report Viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/overview%}) or a [ReportProcessor](/api/telerik.reporting.processing.reportprocessor).
|
||||
|
||||
The [ReportProcessor has an Error event](/api/telerik.reporting.processing.reportprocessor#Telerik_Reporting_Processing_ReportProcessor_Error) allowing you to handle general problems with reports without breaking the application. All Report Viewers have Error events allowing you to customize the error message and to handle it in code. Standard error messages are included in the localization resources of the report viewers:
|
||||
The [ReportProcessor has an Error event](/api/telerik.reporting.processing.reportprocessor#Telerik_Reporting_Processing_ReportProcessor_Error) allows you to handle general problems with reports without breaking the application. All Report Viewers have Error events allowing you to customize the error message and handle it in code. Standard error messages are included in the localization resources of the report viewers:
|
||||
|
||||
* **HTML5 Viewer**: [error event]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/api-reference/reportviewer/events/error(e,-args)%}) and [localization resources]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/customizing/localization%});
|
||||
* **WinForms ReportViewer**: [Error event](/api/telerik.reportviewer.winforms.reportviewerbase#Telerik_ReportViewer_WinForms_ReportViewerBase_Error) and [localization resources]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/windows-forms-application/report-viewer-localization%});
|
||||
|
|
@ -50,7 +50,7 @@ Telerik Reporting provides mechanisms for custom handling errors, where you can
|
|||
3. **Errors related to the functionality of the instance processing the report (Report Viewers or ReportProcessor)**.
|
||||
|
||||
* If the error is not breaking the execution of the application, you will be able to use the Error event and localization resources of the corresponding Report Viewer, or the ReportProcessor instance.
|
||||
* More serious problems will have to be handled on application level. For example, if there is a configuration problem with the HTML5 Viewer, you can catch requests and response and redirect to an error page.
|
||||
* More serious problems will have to be handled on the application level. For example, if there is a configuration problem with the HTML5 Viewer, you can catch requests and responses and redirect to an error page.
|
||||
|
||||
## See Also
|
||||
|
||||
|
|
|
|||
|
|
@ -25,20 +25,20 @@ __Telerik Reporting__ produces Excel files in:
|
|||
* Microsoft Excel 2007 and above (OpenXML 2.0). This rendering extension requires [Third-Party Dependencies]({%slug telerikreporting/using-reports-in-applications/third-party-dependencies%}).
|
||||
* Microsoft Excel 97-2003 (BIFF, v.8)
|
||||
|
||||
Telerik Reporting does not rely on Microsoft Office being installed in order to export to both formats. __Microsoft Excel 97-2003__ files can be opened by Microsoft Excel 97 for Windows and later.
|
||||
Telerik Reporting does not rely on Microsoft Office being installed to export to both formats. __Microsoft Excel 97-2003__ files can be opened by Microsoft Excel 97 for Windows and later.
|
||||
|
||||
__Microsoft Excel 2007__ files can be opened by Microsoft Excel 2007 for Windows and later and has the following advantages over __Microsoft Excel 97-2003__ :
|
||||
|
||||
* Works in Medium Trust.
|
||||
* Supports up to 16 million colors.
|
||||
* Hyperlinks support.
|
||||
* Graph items are rendered as Metafiles (EMF). This guarantees best quality in any scale factor and when printing. The format must be considered if the Excel file will be post-processed by third party tool.
|
||||
* Graph items are rendered as Metafiles (EMF). This guarantees the best quality in any scale factor and when printing. The format must be considered if the Excel file will be post-processed by a third-party tool.
|
||||
|
||||
The Excel Rendering Extensions tries to reproduce as much of the original report as possible regarding layout and styling, but there are certain limitations that are imposed by the physical and logical structure of an Excel Document.
|
||||
The Excel Rendering Extensions tries to reproduce as much of the original report as possible regarding layout and styling, but certain limitations are imposed by the physical and logical structure of an Excel Document.
|
||||
|
||||
## Report Item Layout
|
||||
|
||||
* The layout of the generated Excel document is controlled by the device info parameter [SplitWorksheetOnPageBreak]({%slug telerikreporting/using-reports-in-applications/export-and-configure/configure-the-export-formats/overview%}). By default, the entire report is rendered into a single Excel worksheet and the paging is not applied. If the _SplitWorksheetOnPageBreak_ is set to **true**, new worksheet gets generated on each page break configured in the report defintition.
|
||||
* The layout of the generated Excel document is controlled by the device info parameter [SplitWorksheetOnPageBreak]({%slug telerikreporting/using-reports-in-applications/export-and-configure/configure-the-export-formats/overview%}). By default, the entire report is rendered into a single Excel worksheet and the paging is not applied. If the _SplitWorksheetOnPageBreak_ is set to **true**, a new worksheet gets generated on each page break configured in the report definition.
|
||||
* Overlapping items are not supported and will be moved down/right by the Excel renderer so that they do not overlap.
|
||||
* When the TextBox grows vertically to accommodate larger content, Excel may render the text with larger space between the lines.
|
||||
|
||||
|
|
@ -53,7 +53,7 @@ The Excel Rendering Extensions tries to reproduce as much of the original report
|
|||
|
||||
## Page Headers and Footers
|
||||
|
||||
The page header and footer render differently depending on the [Excel 2003 Device Information Settings]({%slug telerikreporting/using-reports-in-applications/export-and-configure/configure-the-export-formats/excel-2003-device-information-settings%}). The page header can be rendered in two ways: as a sequence of frozen rows at the top of the worksheet, or in the native Excel page header. The page footer can also be rendered in two ways: as sequence of excel cells at the bottom of the worksheet or in the native Excel page footer. The native Excel page sections are divided in three – left, middle and right. Report items will enter the respective page footer section according to their original location in design-time.
|
||||
The page header and footer render differently depending on the [Excel 2003 Device Information Settings]({%slug telerikreporting/using-reports-in-applications/export-and-configure/configure-the-export-formats/excel-2003-device-information-settings%}). The page header can be rendered in two ways: as a sequence of frozen rows at the top of the worksheet, or in the native Excel page header. The page footer can also be rendered in two ways: as a sequence of Excel cells at the bottom of the worksheet or in the native Excel page footer. The native Excel page sections are divided into three – left, middle, and right. Report items will enter the respective page footer section according to their original location in design time.
|
||||
|
||||
>note Because of Excel limitations, TextBoxes are the only type of report item that can be rendered in the native Excel header/footer section.
|
||||
|
||||
|
|
@ -76,8 +76,8 @@ Background images are not supported.
|
|||
| Report Item | Rendering Notes |
|
||||
| ------ | ------ |
|
||||
|TextBox|TextBox values are converted to string or number cells in Excel depending on the actual value. If a supported .NET string format is supplied through the Format property of the TextBox, the resulting cell is accordingly formatted respecting the Culture of the TextBox. Item binding expressions are not converted to Excel formulas.|
|
||||
|Graph|Graph report items are rendered as an Excel Picture object and not Excel Chart object. In __Microsoft Excel 97-2003__ it is a Bitmap image; in __Microsoft Excel 2007 and above__ it is a Metafile(EMF).|
|
||||
|Barcode|Barcode is rendered as an Excel Picture object with a Bitmap image. In __Microsoft Excel 97-2003__ it is a Bitmap image; in __Microsoft Excel 2007 and above__ it is a Metafile(EMF). Due to this if the barcode is small, when exported to the __Microsoft Excel 97-2003 (XLS)__ format, the image will be rasterized and the barcode might become unreadable. Exporting to __Microsoft Excel 2007 and above(XLSX)__ is advised because then the image will be in a vector format (EMF) |
|
||||
|Graph|Graph report items are rendered as an Excel Picture object and not an Excel Chart object. In __Microsoft Excel 97-2003__ it is a Bitmap image; in __Microsoft Excel 2007 and above__ it is a Metafile(EMF).|
|
||||
|Barcode|Barcode is rendered as an Excel Picture object with a Bitmap image. In __Microsoft Excel 97-2003__ it is a Bitmap image; in __Microsoft Excel 2007 and above__ it is a Metafile(EMF). Due to this if the barcode is small when exported to the __Microsoft Excel 97-2003 (XLS)__ format, the image will be rasterized and the barcode might become unreadable. Exporting to __Microsoft Excel 2007 and above(XLSX)__ is advised because then the image will be in a vector format (EMF) |
|
||||
|Table|Table is rendered as a range of Excel cells.|
|
||||
|HtmlTextBox|HtmlTextBox is rendered as plain text with no formatting.|
|
||||
|Shape|Shape report items are rendered as Excel Picture objects with Bitmap images, not Microsoft Office Drawings.|
|
||||
|
|
@ -89,13 +89,13 @@ Background images are not supported.
|
|||
|
||||
## Merging Cells
|
||||
|
||||
The Excel renderer is mainly a layout renderer. Its purpose is to replicate the layout of the report being rendered as closely as possibly in an Excel worksheet and consequently cells might be merged in the worksheet to keep the WYSIWYG report layout. Merged cells are possible source for problems, since the sort functionality in Excel requires cells to be merged in a very specific way for sort to work properly e.g. Excel requires that the ranges of merged cells have the same size in order to be sorted.
|
||||
The Excel renderer is mainly a layout renderer. Its purpose is to replicate the layout of the report being rendered as closely as possible in an Excel worksheet and consequently, cells might be merged in the worksheet to keep the WYSIWYG report layout. Merged cells are a possible source for problems since the sort functionality in Excel requires cells to be merged in a very specific way for sort to work properly e.g. Excel requires that the ranges of merged cells have the same size to be sorted.
|
||||
|
||||
If sorting is important for your exported to Excel reports, the guidelines below can help you reduce the number of merged cells in your Excel worksheets, which is the common cause for difficulties with Excel sort functionality:
|
||||
If sorting is important for your exported Excel reports, the guidelines below can help you reduce the number of merged cells in your Excel worksheets, which is the common cause of difficulties with Excel sort functionality:
|
||||
|
||||
* The most common cause of merged cells is improper or missing left/right alignment of report items. Make sure the left and right edges of all report items line up with one another. The alignment and applying the same width to report items will usually solve the problem.
|
||||
* Aligning items precisely might not be enough, and in some rare cases columns might continue to be merged. This is likely caused by internal unit conversion and rounding when the Excel worksheet is rendered. In the report definition, you can specify location and size in different measurement units such as inches, pixels, centimeters, and points, but internally Excel uses points. So in order to minimize conversion and the potential inaccuracy of rounding when converting inches and centimeters to points, consider specifying all measurements in points (one inch is 72 points).
|
||||
* The Page Header of the report interferes with the exported columns in Excel. A horizontal page break (see [Understanding Pagination]({%slug telerikreporting/designing-reports/rendering-and-paging/understanding-pagination%})) that splits a report item in two parts will result in an additional Excel column in the item. For that reason, you need to make sure that the report physical page is wide enough to accommodate the entire report content so that there is no horizontal page break introduced. The report designers indicate when the report is wider than the physical page through a yellow warning triangle at the top left corner of the report. You may check the warning message by hovering over the triangle.
|
||||
* Aligning items precisely might not be enough, and in some rare cases, columns might continue to be merged. This is likely caused by internal unit conversion and rounding when the Excel worksheet is rendered. In the report definition, you can specify location and size in different measurement units such as inches, pixels, centimeters, and points, but internally Excel uses points. So to minimize conversion and the potential inaccuracy of rounding when converting inches and centimeters to points, consider specifying all measurements in points (one inch is 72 points).
|
||||
* The Page Header of the report interferes with the exported columns in Excel. A horizontal page break (see [Understanding Pagination]({%slug telerikreporting/designing-reports/rendering-and-paging/understanding-pagination%})) that splits a report item into two parts will result in an additional Excel column in the item. For that reason, you need to make sure that the report's physical page is wide enough to accommodate the entire report content so that there is no horizontal page break introduced. The report designers indicate when the report is wider than the physical page through a yellow warning triangle at the top left corner of the report. You may check the warning message by hovering over the triangle.
|
||||
|
||||
## Page Settings
|
||||
|
||||
|
|
@ -140,7 +140,7 @@ If any other paper size is specified, the default printer settings will be used.
|
|||
|
||||
## Formatting Strings
|
||||
|
||||
Formatting Strings used in reports are applied on rendering the document in the selected format. To preserve the result from previewing the document, formats are saved as custom formatting strings in the Excel file. Otherwise, culture specififc setting can change the data meaning in the Excel file.
|
||||
Formatting Strings used in reports are applied to rendering the document in the selected format. To preserve the result from previewing the document, formats are saved as custom formatting strings in the Excel file. Otherwise, culture-specific settings can change the data meaning in the Excel file.
|
||||
|
||||
>tip If an item's Value property is evaluated as a string, the Numeric/DateTime formatting string will not be applied.
|
||||
|
||||
|
|
@ -185,25 +185,25 @@ If a valid format string is detected by the rendering extension, the raw value w
|
|||
|
||||
Excel places limitations on exported reports due to the format capabilities. The most significant are the following:
|
||||
|
||||
* TextBoxes are rendered within one Excel cell. Font size, font face, decoration, font style and text/vertical align are the only formatting that is supported on individual text within an Excel cell.
|
||||
* TextBoxes are rendered within one Excel cell. Font size, font face, decoration, font style, and text/vertical alignment are the only formatting that is supported on individual text within an Excel cell.
|
||||
* Telerik Reporting expressions are not converted to Excel formulas. TextBox values that are expressions are evaluated during report processing and the result is exported as content of Excel cell.
|
||||
* Excel does not support background images for individual cells, so Background images for report items (including Report) are ignored.
|
||||
* Excel native page headers and footers support a maximum of 255 characters including [Formatting and VBA Codes for Headers and Footers](https://learn.microsoft.com/en-us/previous-versions/office/developer/office-2007/bb225426(v=office.12)). The rendering extension truncates the string at 255 characters.
|
||||
* Excel does not support Watermarks.
|
||||
* Underlining justified text will only underline the words and not the spaces between them.
|
||||
* Table of contents is not supported.
|
||||
* The maximum length of Excel Worksheet name is 25 characters. Longer names would be trimmed. The limitation set by Microsoft Excel is 31 characters. Six (6) of them are preserved to secure the uniqueness of Worksheet names, for example when exporting a Report Book containing reports with the same Document Name.
|
||||
* The maximum length of the Excel Worksheet name is 25 characters. Longer names would be trimmed. The limitation set by Microsoft Excel is 31 characters. Six (6) of them are preserved to secure the uniqueness of Worksheet names, for example when exporting a Report Book containing reports with the same Document Name.
|
||||
|
||||
### Excel 97-2003
|
||||
|
||||
* Supported only in the `.NET Framework`.
|
||||
* Excel supports a palette of up to 56 colors. The first 56 unique colors used in the report are defined in a custom palette. If more than 56 colors are used in the report, the rendering extension matches the required color to one of the 56 colors already available in the palette. Excel’s color matching algorithm is used to match colors to ones already existing in the palette.
|
||||
* Excel supports a palette of up to 56 colors. The first 56 unique colors used in the report are defined in a custom palette. If more than 56 colors are used in the report, the rendering extension matches the required color to one of the 56 colors already available in the palette. Excel’s color-matching algorithm is used to match colors to ones already existing in the palette.
|
||||
* The maximum number of rows in a worksheet is limited to 65,536. If this is exceeded, the renderer displays an error message.
|
||||
* The maximum number of columns in a worksheet is limited to 256. If this is exceeded, the renderer displays an error message.
|
||||
* The maximum column width is limited to 255 characters or 1726.5 points. The renderer does not verify that the column width is less than the limit.
|
||||
* The maximum row height is 409 points. If the contents of the row cause the row height to increase beyond 409 points, the contents are split and added to the next row instead.
|
||||
* The maximum number of characters in a cell is limited to 32,767. If this is exceeded, the renderer displays an error message.
|
||||
* In FIPS enabled environments a report export in Excel 97-2003 format will fail.
|
||||
* In FIPS-enabled environments a report export in Excel 97-2003 format will fail.
|
||||
* When the result of an expression is not a number (i.e. double.NaN) or infinite value (i.e. double.PositiveInfinity or double.NegativeInfinity) then double.MaxValue or double.Min value will be written to the Excel cell.
|
||||
|
||||
### Excel 2007 and above
|
||||
|
|
|
|||
|
|
@ -17,21 +17,21 @@ The Word rendering extension is based on the Image rendering extension, with som
|
|||
|
||||
## Rendering
|
||||
|
||||
Report exported to Word appears as a nested table that represents both the report layout and content. Nested data region items, such as SubReport, Table, Crosstab or List items are rendered as nested tables that reflect the layout and structure of that data region in the report. Due to the way Word renders these nested items, their borders may be misaligned or appear drawn with double lines if the nested item has its own border style. Other items are rendered as separate cells within the same table. The item’s value is rendered as content in the table cell. PictureBox, Chart, Barcode and Shape items are rendered as static images in the cell. URL actions of TextBox items are rendered as hyperlinks, as soon as they represent absolute URLs. The relative ones are not respected and are not rendered in Word.
|
||||
The report exported to Word appears as a nested table that represents both the report layout and content. Nested data region items, such as SubReport, Table, Crosstab, or List items are rendered as nested tables that reflect the layout and structure of that data region in the report. Due to the way Word renders these nested items, their borders may be misaligned or appear drawn with double lines if the nested item has its own border style. Other items are rendered as separate cells within the same table. The item’s value is rendered as content in the table cell. PictureBox, Chart, Barcode, and Shape items are rendered as static images in the cell. URL actions of TextBox items are rendered as hyperlinks, as soon as they represent absolute URLs. The relative ones are not respected and are not rendered in Word.
|
||||
|
||||
>note Word tables support a maximum of 63 columns. Reports with very complex layout or many misaligned items might sometimes produce documents exceeding that limit. To avoid this, align your items carefully in the designer, using the "snap to lines" and "snap to grid" modes whenever possible. To organize many items together in columns and rows consider using the Table, Crosstab or List report item instead.
|
||||
|
||||
>caution Since report items are rendered as individual table cells they cannot overlap. If you have overlapping items in the report definition, the resulting document is undefined, i.e. this would break the report layout. If there are no overlapping items the original layout is preserved. In general, avoid having overlapping items at design-time if you are planning to export the report to Word.
|
||||
>caution Since report items are rendered as individual table cells they cannot overlap. If you have overlapping items in the report definition, the resulting document is undefined, i.e. this would break the report layout. If there are no overlapping items the original layout is preserved. In general, avoid having overlapping items at design time if you are planning to export the report to Word.
|
||||
|
||||
## Pagination
|
||||
|
||||
Microsoft Word does not support the concept of hard pages. Instead, when the exported document is opened in Word, Word repaginates it again based on the page size. The rendering extension tries to preserve closely the original pages of the report, inserting additional page breaks when necessary. However in some rare cases the repagination performed by Word might interfere with this behavior, resulting in a document with page breaks on unexpected places or blank pages. To correct this, you can try changing the Word’s pagination by adjusting the page margins.
|
||||
Microsoft Word does not support the concept of hard pages. Instead, when the exported document is opened in Word, Word repaginates it again based on the page size. The rendering extension tries to preserve closely the original pages of the report, inserting additional page breaks when necessary. However, in some rare cases, the repagination performed by Word might interfere with this behavior, resulting in a document with page breaks on unexpected places or blank pages. To correct this, you can try changing the Word’s pagination by adjusting the page margins.
|
||||
|
||||
##Page Sizing
|
||||
|
||||
When the report is rendered, the page size, orientation and margins are configured in the document according to the corresponding properties in the report definition. For ReportBook the page settings of each individual report in the book are respected. This can produce a document with varying page sizes and orientation per report.
|
||||
When the report is rendered, the page size, orientation, and margins are configured in the document according to the corresponding properties in the report definition. For ReportBook the page settings of each individual report in the book are respected. This can produce a document with varying page sizes and orientation per report.
|
||||
|
||||
>note Word supports a maximum page size of 22 inches wide and 22 inches high. If your page is wider than 22 inches, some data may not be displayed in Print Layout view.
|
||||
>note Word supports a maximum page size of 22 inches wide and 22 inches high. If your page is wider than 22 inches, some data may not be displayed in the Print Layout view.
|
||||
|
||||
##Page Headers and Footers
|
||||
|
||||
|
|
@ -43,31 +43,32 @@ Word does not support configuring explicitly the height of headers and footers.
|
|||
|
||||
Newsletter-style multi-column reports are rendered as multiple columns in Word.
|
||||
|
||||
Since Word repaginates the entire document when opening it, the same behavior is applied to multi-column documents as well. The rendering extension tries to preserve the original organization of the report in columns by inserting column breaks when necessary. However in some rare occasions the repagination performed by Word might interfere with this behavior resulting in column breaks on unexpected places or empty columns. To correct this, you can try changing the Word’s pagination by adjusting the column spacing or page margins.
|
||||
Since Word repaginates the entire document when opening it, the same behavior is applied to multi-column documents as well. The rendering extension tries to preserve the original organization of the report in columns by inserting column breaks when necessary. However, in some rare occasions, the repagination performed by Word might interfere with this behavior resulting in column breaks in unexpected places or empty columns. To correct this, you can try changing the Word’s pagination by adjusting the column spacing or page margins.
|
||||
|
||||
## Styling
|
||||
|
||||
The following is a brief description of how styles are rendered in Word.
|
||||
|
||||
* `Colors` - Colors are rendered as exact RGB values. Transparent colors with alpha channel are not supported.
|
||||
* `Borders` - Borders of report items are rendered as table cell borders. Borders of adjacent report items are collapsed automatically, following the Word’s own border collapse rules.
|
||||
* `Colors` - Colors are rendered as exact RGB values. Transparent colors with alpha channels are not supported.
|
||||
* `Borders` - Borders of report items are rendered as table cell borders. Borders of adjacent report items are collapsed automatically, following the Word’s own border-collapse rules.
|
||||
|
||||
>note Word application applies a margin value to the table cell by default. This will produce a space between the nested table borders and the parent table borders. To remove the space, the margin needs to be removed manually after opening the document in MS Word.
|
||||
|
||||
* `Background` - Background colors are rendered as background shading of table cells. Background images are not supported.
|
||||
* `Fonts` - Fonts and their settings are rendered exactly as they are specified in the report definition. In order to display correctly a document that uses a specific font, that font must be installed on the client machine. The rendering extension does not provide a fallback mechanism in case of missing fonts.
|
||||
* `Fonts` - Fonts and their settings are rendered exactly as they are specified in the report definition. To display correctly a document that uses a specific font, that font must be installed on the client machine. The rendering extension does not provide a fallback mechanism in case of missing fonts.
|
||||
|
||||
>note Text boxes which do not contain a value (contain a null value, empty string, etc.) will be rendered with font size of 1pt.
|
||||
>note Text boxes that do not contain a value (contain a null value, empty string, etc.) will be rendered with a font size of 1pt.
|
||||
|
||||
* `Text` - Text justification and alignment is preserved when exporting to Word. Note that if a justified text goes from one page to another, the last line of the first page will be left-aligned. Text orientation is supported only for the angles of 0, 90 and 270 degrees. Rotated text on other angles is not supported and is approximated to the closest match.
|
||||
* `Text` - Text justification and alignment are preserved when exporting to Word. Note that if a justified text goes from one page to another, the last line of the first page will be left-aligned. Text orientation is supported only for the angles of 0, 90, and 270 degrees. Rotated text on other angles is not supported and is approximated to the closest match.
|
||||
* `HTML` - HTML text is rendered using Word’s own HTML rendering engine. This might produce a result that is slightly different from the output generated in Web browsers.
|
||||
|
||||
## Report items
|
||||
|
||||
The following rules apply to rendered report items:
|
||||
|
||||
* The PictureBox report item's Sizing property should be set to AutoSize for best image quality or the PictureBox.Size should match the actual image size. In case you get a blurred image at run-time, change the Sizing mode or resize the PictureBox item to match the size of the produced image.
|
||||
* The Cross-section item renders its graphical primitives as images. It is recommended to set the *Position* property to `Front` to allow rendering it on top of the other items, otherwise the Word application may apply undesired offset to it.
|
||||
* The [PictureBox report item]({%slug telerikreporting/designing-reports/report-structure/picturebox%})'s Sizing property should be set to AutoSize for best image quality or the PictureBox.Size should match the actual image size. In case you get a blurred image at run-time, change the Sizing mode or resize the PictureBox item to match the size of the produced image.
|
||||
* The [Cross-Section item]({%slug telerikreporting/designing-reports/report-structure/cross-section-item%}) renders its graphical primitives as images. It is recommended to set the *Position* property to `Front` to allow rendering it on top of the other items. Otherwise, the Word application may apply an undesired offset to it.
|
||||
* The [Checkbox item]({%slug telerikreporting/designing-reports/report-structure/checkbox%}) is rendered in two parts. The _Checked_ status is shown as an image, and the _Text_ value is displayed as text beside it.
|
||||
|
||||
## Interactivity
|
||||
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче