# Major Properties and Settings of Report Item The Report item contains several specific properties that control the design-time and run-time behavior as well as the general layout and functionality of the generated report documents. ## DocumentName The [DocumentName](https://www.telerik.com/products/reporting/documentation/api/telerik.reporting.report#Telerik_Reporting_Report_DocumentName) specifies the default document name when exporting from a Report Viewer. The Standalone Report Designer won't use `DocumentName` when exporting. It will rather use the Report `Name`. The `DocumentName` may be set to a [report expression](https://www.telerik.com/products/reporting/documentation/designing-reports/connecting-to-data/expressions/overview) containing [Report Parameters](https://www.telerik.com/products/reporting/documentation/designing-reports/connecting-to-data/report-parameters/overview) and other [Global Objects](https://www.telerik.com/products/reporting/documentation/designing-reports/connecting-to-data/expressions/expressions-reference/global-objects). The DataSource fields are not accessible at this Report level and cannot be used - see [expression scope](https://www.telerik.com/products/reporting/documentation/designing-reports/connecting-to-data/expressions/expression-scope) for more details. ## Paging The Report item delivers the `PageSettings` and `PageNumberingStyle` settings for controlling the paging functionality. ### PageSettings The [PageSettings](https://www.telerik.com/products/reporting/documentation/api/telerik.reporting.drawing.pagesettings) property determines the layout of the report document in physical page formats like PDF and when printed on paper. This includes the page size, watermarks, [number of columns](https://www.telerik.com/products/reporting/documentation/report-items/report-item/multi-column-reports), and so on. The `PageSettings` are entirely respected in physical (hard) pagination formats, whereas some of them are ignored in soft pagination formats. The difference is explained in the article on [interactive and print layout](https://www.telerik.com/products/reporting/documentation/embedding-reports/display-reports-in-applications/interactive-vs.-print-layout). ### PageNumberingStyle The [PageNumberingStyle](https://www.telerik.com/products/reporting/documentation/api/telerik.reporting.report#Telerik_Reporting_Report_PageNumberingStyle) property is related only to the [paging of report books](https://www.telerik.com/products/reporting/documentation/designing-reports/report-book/report-book-paging) and determines whether to restart the page count with each report. ## Report Parameters The [Report parameters](https://www.telerik.com/products/reporting/documentation/designing-reports/connecting-to-data/report-parameters/overview) are [global objects](https://www.telerik.com/products/reporting/documentation/designing-reports/connecting-to-data/expressions/expressions-reference/global-objects) that can be used all over the Report. Their main application is for filtering the report data, but they can also be used for passing external information to the Report and for other purposes. For more detailed information, refer to the following articles: * [Adding Report Parameters](https://www.telerik.com/products/reporting/documentation/designing-reports/connecting-to-data/report-parameters/how-to-add-report-parameters) * [Using Report Parameters in Expressions](https://www.telerik.com/products/reporting/documentation/designing-reports/connecting-to-data/report-parameters/using-report-parameters-in-expressions) * [Using Multi-Value Parameters](https://www.telerik.com/products/reporting/documentation/designing-reports/connecting-to-data/report-parameters/using-multivalue-parameters) * [Cascading Parameters with Applied Filtering on Report Level](https://www.telerik.com/products/reporting/documentation/designing-reports/connecting-to-data/report-parameters/how-to-cascade-parameters-with-applied-filtering-on-report-level) * [Cascading Parameters with Applied Filtering on Data Source Level](https://www.telerik.com/products/reporting/documentation/designing-reports/connecting-to-data/report-parameters/how-to-cascade-parameters-with-applied-filtering-on-data-source-level) ## Rendering and Processing The Report item exposes a set of properties that allow you to control some aspects of its processing and rendering. * `AutoRun`— As of [2024 Q4 (18.3.24.1112)](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-2024-q4-18-3-24-1112), the report author can control the initial automatic report rendering process by using the [AutoRun](https://www.telerik.com/products/reporting/documentation/api/telerik.reporting.report#Telerik_Reporting_Report_AutoRun) property. By default, `AutoRun` is `True`. When `AutoRun=True`, the report loading behavior does not change: the report is automatically loaded if all parameters have valid values, or waits until all parameter values are valid. When `AutoRun=False`: * The Report Viewer displays the **Preview** button in the Parameters Area even if all [Report Parameters](https://www.telerik.com/products/reporting/documentation/designing-reports/connecting-to-data/report-parameters/overview) have [AutoRefresh](https://www.telerik.com/products/reporting/documentation/api/telerik.reporting.reportparameter#Telerik_Reporting_ReportParameter_AutoRefresh) set to `True`. * If all [Report Parameters](https://www.telerik.com/products/reporting/documentation/designing-reports/connecting-to-data/report-parameters/overview) have valid values, the Report Viewer does not trigger report rendering and displays a prompt message in the Report Area to the end user with information on how they may trigger the rendering(*by clicking on the Preview button*). * `SkipBlankPages`— As of [R1 2021 SP1 (15.0.21.224)](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-r1-2021-sp1-15-0-21-224), you can indicate to the Reporting engine whether to ignore the pages with non-significant content by using the [SkipBlankPages](https://www.telerik.com/products/reporting/documentation/api/telerik.reporting.report#Telerik_Reporting_Report_SkipBlankPages) property. By default, `SkipBlankPages` is `True`. For example, `SkipBlankPages` may be kept `True` to remove the empty pages due to horizontal page breaks. For more information, refer to the articles on [horizontal paging](https://www.telerik.com/products/reporting/documentation/styling/rendering-and-paging/understanding-pagination#horizontal-paging) and on [skipping blank pages in the rendered report](https://www.telerik.com/products/reporting/documentation/styling/rendering-and-paging/understanding-rendering-behaviors#skip-blank-pages-in-the-rendered-report). * `RuntimeSettings`— As of [R2 2021 (15.1.21.512)](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-r2-2021-15-1-21-512), you can specify [device information settings](https://www.telerik.com/products/reporting/documentation/doc-output/configure-the-export-formats/overview) per particular report as part of its definition by configuring the [RuntimeSettings](https://www.telerik.com/products/reporting/documentation/api/telerik.reporting.report#Telerik_Reporting_Report_RuntimeSettings) report property. Apart from setting the export parameters for a particular extension, `RuntimeSettings` allows you to hide it and change its description when listed to the end-user. * `ReportEngineSettings`— As of [R3 2022 SP1 (16.2.22.1109)](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-r3-2022-sp1-16-2-22-1109), you can set the property [CacheDefinitionProperties](https://www.telerik.com/products/reporting/documentation/api/telerik.reporting.reportenginesettings#Telerik_Reporting_ReportEngineSettings_CacheDefinitionProperties) per particular report as part of its definition by configuring it as an element of the [ReportEngineSettings](https://www.telerik.com/products/reporting/documentation/api/telerik.reporting.report#Telerik_Reporting_Report_ReportEngineSettings) report property. The available values are described in the API Reference in [Enum CacheDefinitionProperties](https://www.telerik.com/products/reporting/documentation/api/telerik.reporting.cachedefinitionproperties). Setting the property to `Yes`/`No` would force the Reporting engine to enable/disable the property for the specific report. Selecting `Default` would let the Reporting engine use the 'cacheDefinitionProperties' key in the 'processing' element from the application configuration file - [processing Element](https://www.telerik.com/products/reporting/documentation/doc-output/configure-the-report-engine/processing-element). * `Localizable`—To start localizing the report, set the `Localizable` property to `True`. For more information about the localization procedure, refer to the article on [localizing reports](https://www.telerik.com/products/reporting/documentation/globalization/localization). > If at any point the `Localizable` property is set to `False`, all resource files are deleted and the report property values are filled with the currently selected language values. ## Styling and Design The Report item exposes a set of properties that allow you to control styling and other design-time-related processes. * `StyleSheet`— Enables you to create custom styles through a built-in styling model that is similar to CSS. You can assign these styles by using CSS selectors such as `Type`, `Attribute`, `Style`, and `Descendant`. For more information about the process, refer to the following articles: * [Using Styles to Customize Reports](https://www.telerik.com/products/reporting/documentation/styling/styling-reports/using-styles-to-customize-reports) * [Creating Style Rules](https://www.telerik.com/products/reporting/documentation/styling/styling-reports/creating-style-rules) * [Understanding Style Selectors](https://www.telerik.com/products/reporting/documentation/styling/styling-reports/understanding-style-selectors) * [Style Inheritance and Overriding](https://www.telerik.com/products/reporting/documentation/styling/styling-reports/style-inheritance-and-overriding) * `ExternalStyleSheets`— Imports StyleSheets previously created and stored in XML files. For more information, refer to the article on [exporting and reusing stylesheets](https://www.telerik.com/products/reporting/documentation/styling/styling-reports/exporting-and-reusing-style-sheets). * `UnitOfMeasure`— Specifies the default unit of measure for the report. All newly created report items will have their locations, sizes, and so on in this [UnitType](https://www.telerik.com/products/reporting/documentation/api/telerik.reporting.drawing.unittype). For new reports, the unit of measure is automatically determined based on the machine's regional settings - if the current machine uses metric culture, the default unit of measure will be set to *cm*, otherwise - *inch*. * `SnapGridSize`— Controls the step of the `Rulers` in the [Standalone Report Designer](https://www.telerik.com/products/reporting/documentation/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview#major-ui-elements-in-the-standalone-report-designer) and in the [Visual Studio Report Designer](https://www.telerik.com/products/reporting/documentation/designing-reports/report-designer-tools/desktop-designers/visual-studio-report-designer/overview). ## See Also * [Getting Started with the Report Item](https://www.telerik.com/products/reporting/documentation/report-items/report-item/get-started) * [Page Headers and Footers](https://www.telerik.com/products/reporting/documentation/report-items/report-item/page-headers-footers) * [Report Headers and Footers](https://www.telerik.com/products/reporting/documentation/report-items/report-item/report-headers-footers) * [Creating Multi-Column Reports](https://www.telerik.com/products/reporting/documentation/report-items/report-item/multi-column-reports)