diff --git a/designing-reports/connecting-to-data/data-source-components/sqldatasource-component/using-data-providers/using-sqlite-data-provider.md b/designing-reports/connecting-to-data/data-source-components/sqldatasource-component/using-data-providers/using-sqlite-data-provider.md index 9afb5ea9d..346427cec 100644 --- a/designing-reports/connecting-to-data/data-source-components/sqldatasource-component/using-data-providers/using-sqlite-data-provider.md +++ b/designing-reports/connecting-to-data/data-source-components/sqldatasource-component/using-data-providers/using-sqlite-data-provider.md @@ -1,7 +1,7 @@ --- title: Using the SQLite Data Provider page_title: Integrating the SQLite Data Provider -description: "Learn more about how the SQLite data provider can be used by the SqlDataSource component to connect to local data storages in Telerik Reporting." +description: "Learn more about how the SQLite data provider can be used by the SqlDataSource component to connect to local data storage in Telerik Reporting." slug: telerikreporting/designing-reports/connecting-to-data/data-source-components/sqldatasource-component/using-data-providers/using-sqlite-data-provider tags: System.Data.Sqlite,sqlite,data,provider published: True @@ -15,11 +15,11 @@ The [System.Data.SQLite](https://system.data.sqlite.org/) is an ADO.NET provider ## Setting up the System.Data.Sqlite Data Provider in the .NET Standalone Report Designer 1. Download the **SQLite Binaries** built for `.NET Standard 2.0` or `.NET Standard 2.1` from the [System.Data.Sqlite](http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki) Downloads page. -1. Unpackage the zip with the binaries and copy the `System.Data.Sqlite.dll` file to the .NET Standalone Report Designer installation directory e.g. `C:\Program Files (x86)\Progress\Telerik Reporting {{site.suiteversion}}\Report Designer\.NET`. -1. Download SQLite binaries built for `.NET Framework.4.X` from the [System.Data.Sqlite](http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki) page, for example [sqlite-netFx40-binary-x64-2010-1.0.117.0.zip](https://system.data.sqlite.org/downloads/1.0.117.0/sqlite-netFx40-binary-x64-2010-1.0.117.0.zip). -1. Unpackage the archive and copy the `SQLite.Interop.dll` assembly to the .NET Standalone Report Designer installation directory e.g. `C:\Program Files (x86)\Progress\Telerik Reporting {{site.suiteversion}}\Report Designer\.NET`. +1. Unpackage the zip with the binaries and copy the `System.Data.Sqlite.dll` file to the .NET Standalone Report Designer installation directory, e.g., `C:\Program Files (x86)\Progress\Telerik Reporting {{site.suiteversion}}\Report Designer\.NET`. +1. Download SQLite binaries built for `.NET Framework.4.X` from the [System.Data.Sqlite](http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki) page. +1. Unpackage the archive and copy the `SQLite.Interop.dll` assembly to the .NET Standalone Report Designer installation directory, e.g., `C:\Program Files (x86)\Progress\Telerik Reporting {{site.suiteversion}}\Report Designer\.NET`. 1. Restart the designer if you have previously opened it. -1. Add a new SqlDataSource and you should see that the `Sqlite` Data Provider is in the dropdown. +1. Add a new SqlDataSource, and you should see that the `Sqlite` Data Provider is in the dropdown. ## Setting up the System.Data.Sqlite Data Provider in the .NET Framework Standalone Report Designer @@ -48,7 +48,7 @@ The [System.Data.SQLite](https://system.data.sqlite.org/) is an ADO.NET provider The [System.Data.Sqlite](https://system.data.sqlite.org/) data provider is automatically registered in the `Telerik.Reporting.Processing.Data.DbProviderFactories`. To use this data provider, it should be enough to install the [System.Data.SQLite](https://www.nuget.org/packages/System.Data.SQLite/) NuGet package to the project. -If the [SqlDataSource component]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/sqldatasource-component/overview%}) uses a `shared` connection where it is retrieved from the configuration file of the project(e.g. `appsettings.json`), the provider name must be specified in the connection. For example: +If the [SqlDataSource component]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/sqldatasource-component/overview%}) uses a `shared` connection where it is retrieved from the configuration file of the project(e.g., `appsettings.json`), the provider name must be specified in the connection. For example: ````JSON { diff --git a/embedding-reports/host-the-report-engine-remotely/asp.net-web-api-implementation/how-to-implement-the-reportscontroller-in-an-application.md b/embedding-reports/host-the-report-engine-remotely/asp.net-web-api-implementation/how-to-implement-the-reportscontroller-in-an-application.md index 04213bf3f..3ede360c2 100644 --- a/embedding-reports/host-the-report-engine-remotely/asp.net-web-api-implementation/how-to-implement-the-reportscontroller-in-an-application.md +++ b/embedding-reports/host-the-report-engine-remotely/asp.net-web-api-implementation/how-to-implement-the-reportscontroller-in-an-application.md @@ -11,7 +11,7 @@ previous_url: /telerik-reporting-rest-implementing-http-service,/embedding-repor # Implementing the ReportsController in an ASP.NET Application -The Telerik Reporting REST Web API service is represented by the abstract [ReportsControllerBase](/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase) class. This abstract class requires [IReportSourceResolver](/api/Telerik.Reporting.Services.IReportSourceResolver) and [IStorage](/api/Telerik.Reporting.Cache.Interfaces.IStorage) implementations. In order to add the reports controller to your application follow the steps: +The Telerik Reporting REST Web API service is represented by the abstract [ReportsControllerBase](/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase) class. This abstract class requires [IReportSourceResolver](/api/Telerik.Reporting.Services.IReportSourceResolver) and [IStorage](/api/Telerik.Reporting.Cache.Interfaces.IStorage) implementations. To add the reports controller to your application, follow the steps: 1. Add references to the following Telerik Reporting assemblies (required) and set their __Copy Local__ properties to true in Visual Studio: @@ -20,12 +20,12 @@ The Telerik Reporting REST Web API service is represented by the abstract [Repor 1. Add references to the following Telerik Reporting assemblies (optional) and set their __Copy Local__ properties to true in Visual Studio: - + Telerik.Reporting.Cache.Database.dll - only if [DatabaseStorage](/api/Telerik.Reporting.Cache.Database.DatabaseStorage) caching mechanism is intended. For more details check [Reporting REST Service Storage]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/rest-service-storage/overview%}). The assembly has dependencies on Telerik Data Access which can be checked in the version corresponding [Upgrade article]({%slug telerikreporting/upgrade/overview%}); + + Telerik.Reporting.Cache.Database.dll - only if [DatabaseStorage](/api/Telerik.Reporting.Cache.Database.DatabaseStorage) caching mechanism is intended. For more details, check [Reporting REST Service Storage]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/rest-service-storage/overview%}). The assembly has dependencies on Telerik Data Access, which can be checked in the version corresponding to [Upgrade article]({%slug telerikreporting/upgrade/overview%}); + Telerik.Reporting.OpenXmlRendering - depends on [Third-Party Dependencies]({%slug telerikreporting/using-reports-in-applications/third-party-dependencies%}). Required if you need to export in OpenXML formats (DOCX, PPTX, XLSX); + Telerik.Reporting.XpsRendering - required if you need to export in XPS format; + Telerik.Reporting.Adomd.dll - required if you use [CubeDataSource]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/cubedatasource-component/overview%}) components in reports. The assembly has dependencies on *Microsoft.AnalysisServices.AdomdClient.dll* v.10.0.0.0 or [above with proper binding redirects]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/cubedatasource-component/configuring-your-project-for-using-microsoft-analysis-services%}); - >Without setting Telerik Reporting references' _Copy Local_ to true the assemblies may not be loaded correctly on running the application. + >Without setting Telerik Reporting references' _Copy Local_ to true, the assemblies may not be loaded correctly when running the application. 1. Inherit this base class in your hosting application (usually in the Controllers folder of an MVC application). @@ -36,7 +36,7 @@ The Telerik Reporting REST Web API service is represented by the abstract [Repor {{source=CodeSnippets\MvcCS\Controllers\ReportsController.cs region=ReportsControllerImplementation}} {{source=CodeSnippets\MvcVB\Controllers\ReportsController.vb region=ReportsControllerImplementation}} - >note Starting with the [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)), it is possible to define the [ReportServiceConfiguration](/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase#Telerik_Reporting_Services_WebApi_ReportsControllerBase_ReportServiceConfiguration) with less code using the `AddTelerikReporting` extension method: + >note Starting with the [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), it is possible to define the [ReportServiceConfiguration](/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase#Telerik_Reporting_Services_WebApi_ReportsControllerBase_ReportServiceConfiguration) with less code using the `AddTelerikReporting` extension method: {{source=CodeSnippets\MvcCS\Controllers\ReportsController.cs region=ReportsControllerImplementationMinimal}} {{source=CodeSnippets\MvcVB\Controllers\ReportsController.vb region=ReportsControllerImplementationMinimal}} diff --git a/getting-started/web-designer/improving-basic-report.md b/getting-started/web-designer/improving-basic-report.md index e0b4aea44..5366317c8 100644 --- a/getting-started/web-designer/improving-basic-report.md +++ b/getting-started/web-designer/improving-basic-report.md @@ -3,7 +3,7 @@ title: Improving Basic Report page_title: Improving Your First Report description: "Learn how to edit reports in the Telerik Web Report Designer, add SharedDataSources and Actions, copy content between reports, and more in this step-by-step tutorial." slug: telerikreporting/getting-started/web-designer/improving-basic-report -tags: how,web,designer,report,navigate,action,shareddatasource +tags: web,designer,report,navigate,action,shareddatasource published: True position: 2 --- @@ -12,8 +12,8 @@ position: 2 In this step-by-step tutorial, we will improve the basic report created in the previous tutorial [Embedding the Web Report Designer in .NET {{site.mindotnetversion}} and Creating Your First Report]({%slug telerikreporting/getting-started/web-designer/set-up-and-create-basic-report%}) by adding a common business requirement to click a data series to show more details in a child report. -* First, we will create a second report to display the details data. -* Then, we will learn how to add a [SharedDataSource component]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/shareddatasource-component%}) to share data source between reports. +* First, we will create a second report to display the detailed data. +* Then, we will learn how to add a [SharedDataSource component]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/shareddatasource-component%}) to share a data source between reports. * Next, we will add and configure a [PieChart]({%slug telerikreporting/designing-reports/report-structure/graph/chart-types/pie-charts/overview%}) to the detailed report. * Finally, we will learn how to add a [Drillthrough/Navigate To Report Action]({%slug telerikreporting/designing-reports/adding-interactivity-to-reports/actions/drillthrough-report-action%}) to the master report Column Chart. * At the end, we will have a master report able to navigate to a child report with detailed data for the selected **Product Category**. @@ -93,7 +93,7 @@ Our first goal is to create a new report within the Web Report Designer. It will ![Adding an existing shared data source to the child report from the Assets manager.](images/add-existing-shared-data-source.png) - 1. In the popped-up `Browse For Folder` dialog select `Shared Data Sources` on the left and choose the `productSalesData.sdsx` file, which is our shared data source that we just saved from the main report. + 1. In the popped-up `Browse For Folder` dialog, select `Shared Data Sources` on the left and choose the `productSalesData.sdsx` file, which is our shared data source that we just saved from the main report. ![Selecting an existing shared data source SDSX file from the 'Browse For Folder' dialog in the child report.](images/select-existing-shared-data-source.png) @@ -131,7 +131,7 @@ Our first goal is to create a new report within the Web Report Designer. It will * Check the `DataPointLabelConnectorStyle` > `Visible` property. * Set `DataPointLabelOffset` to `5mm`. - * For `DataPointLabelAlignment` use `OutsideColumn` from the dropdown. + * For `DataPointLabelAlignment`, use `OutsideColumn` from the dropdown. * Click `Save`. ![Styling the pie chart series' data point labels in the child report.](images/pie-chart-series-datapointlabelalignment.png) @@ -144,10 +144,10 @@ Our first goal is to create a new report within the Web Report Designer. It will 1. Navigate to the main report. 1. Search for `category group` in the Search box and select the `productCategoryGroup1`. - 1. In the `Edit Item` dialog go to `Action` and select `Navigate to report` from the dropdown. + 1. In the `Edit Item` dialog, go to `Action` and select `Navigate to report` from the dropdown. 1. Set the _Report source_ `Type` to __UriReportSource__. 1. Open the Assets manager from the icon next to `Uri` and select the `SalesBySubcategory.trdp` report from the `Demo` folder. - 1. Add a new Parameter to the `Parameters` collection of the _Report source_ with `Name` corresponding to the child report's parameter, i.e. `Category`, and `Value` being the value of the current product category field, i.e. `=Fields.ProductCategory`. + 1. Add a new Parameter to the `Parameters` collection of the _Report source_ with `Name` corresponding to the child report's parameter, i.e., `Category`, and `Value` being the value of the current product category field, i.e., `=Fields.ProductCategory`. 1. Click `Save` to preserve the configuration. ![The column chart in the main report with configured Navigate to Report action.](images/navigate-to-report-action-in-main-report-chart.png) @@ -166,7 +166,7 @@ Our first goal is to create a new report within the Web Report Designer. It will * [Video tutorial 'Getting Started with the Web Report Designer: Part 2'](https://www.youtube.com/watch?v=DXKlgq-MYIU) * [Video tutorial 'Getting Started with the Web Report Designer: Part 1'](https://www.youtube.com/watch?v=L-utkcB8-5c) * [Embedding the Web Report Designer in .NET {{site.mindotnetversion}} and Creating Your First Report]({%slug telerikreporting/getting-started/web-designer/set-up-and-create-basic-report%}) -* [Web Report Designer](%{slug telerikreporting/designing-reports/report-designer-tools/web-report-designer/overview%}) +* [Web Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/web-report-designer/overview%}) * [Demo Page for Telerik Reporting](https://demos.telerik.com/reporting) * [Telerik Reporting Homepage](https://www.telerik.com/products/reporting) * [Reporting Forums](https://www.telerik.com/forums/reporting) diff --git a/getting-started/web-designer/set-up-and-create-basic-report.md b/getting-started/web-designer/set-up-and-create-basic-report.md index dd55af7eb..4e46f8c47 100644 --- a/getting-started/web-designer/set-up-and-create-basic-report.md +++ b/getting-started/web-designer/set-up-and-create-basic-report.md @@ -1,9 +1,9 @@ --- -title: Setting up Designer and Creating Basic Report +title: Setting up Designer and Creating a Basic Report page_title: Embedding the Web Report Designer in .NET 8 and Creating Your First Report -description: "Learn how to set up the Telerik Web Report Designer in .NET 8 applications via the Visual Studio Item Templates and how to create a report with Logo and Graph in this step by step tutorial." +description: "Learn how to set up the Telerik Web Report Designer in .NET 8 applications via the Visual Studio Item Templates and how to create a report with Logo and Graph in this step-by-step tutorial." slug: telerikreporting/getting-started/web-designer/set-up-and-create-basic-report -tags: how,configure,.net,applications,web,designer,report +tags: configure,.net,applications,web,designer,report published: True position: 1 previous_url: /getting-started/web-designer/ @@ -13,10 +13,10 @@ previous_url: /getting-started/web-designer/ This is a step-by-step tutorial that shows how to integrate the [Web Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/web-report-designer/overview%}) in `.NET {{site.mindotnetversion}}` ASP.NET Core application in Visual Studio 2022. -* First, you will create a Web Application and add Telerik Web Report Designer through its Visual Studio Item Template. +* First, you will create a Web Application and add the Telerik Web Report Designer through its Visual Studio Item Template. * Next, you'll create and style a new report. * Then, you will add a remote DataSource and connect it to a new Graph in the report. -* At the end you will have a web application with embedded Telerik Web Report Designer with the default `SampleReport.trdp` and the newly created `ProductSales.trdp` reports in its storage that you may preview and edit. +* At the end, you will have a web application with embedded Telerik Web Report Designer with the default `SampleReport.trdp` and the newly created `ProductSales.trdp` reports in its storage that you may preview and edit. ![Preview of the base report created from scratch in the web report designer.](images/preview-base-report-web-designer.png) @@ -33,7 +33,7 @@ Let's create an ASP.NET Core application in Visual Studio and embed the Telerik ![Open the menu for adding new item to your project through Visual Studio item template.](images/add-vs-item-template.png) - 1. You may search for `telerik reporting` to list the available Reporting item templates. Add `Telerik Web Report Designer HTML5 Page {{site.suiteversion}}`. The version may vary, depending on the last Reporting version installed. + 1. You may search for `Telerik Reporting` to list the available Reporting item templates. Add `Telerik Web Report Designer HTML5 Page {{site.suiteversion}}`. The version may vary, depending on the last Reporting version installed. 1. Name the new page `webReportDesigner.html` (this is the default name). ![Searcing for and adding Web Report Desiger page 'webReportDesigner.html' through the Visual Studio item template.](images/add-web-report-designer-page.png) @@ -46,21 +46,21 @@ Let's create an ASP.NET Core application in Visual Studio and embed the Telerik ![Create new Web Report Desiger REST Service in the project through the wizard's 'Configure web report designer engine' page.](images/create-new-rest-service.png) - 1. On the next step the wizard will ask for the initial report to load. Select the `Sample report definition` option to create a new sample report if you don't have any. + 1. On the next step, the wizard will ask for the initial report to load. Select the `Sample report definition` option to create a new sample report if you don't have any. ![Create sample report definition through the wizard's 'Configure report' page.](images/create-sample-report.png) - 1. When you click `Finish` you should see a status page confirming that everything was set up correctly. + 1. When you click `Finish`, you should see a status page confirming that everything was set up correctly. 1. (optional) Open the file `launchSetting.json` in the folder `Properties` and add the next line, setting the opening page to the "profiles" > "Telerik.WRD.GettingStarted" object. Note that the name of the project and the web page may vary: `"launchUrl": "webReportDesigner.html"`. - ![The 'launchSetting.json' file in project folder 'Properties' with added 'launchUrl'.](images/launch-setting-json.png) + ![The 'launchSetting.json' file in the project folder 'Properties' with added 'launchUrl'.](images/launch-setting-json.png) 1. Run the project. If everything is fine, you should see the web page with the designer with the sample report opened, and the onboarding guide to walk you through the main tools in the designer. - We recommend getting familiar with the Web Report Designer by clicking on the `Next` button in the guide. You may skip the guide at any step through the button `End Tour`. Pay attention to the Search functionality of the designer that lets you locate any report item, section, or property easily. + We recommend getting familiar with the Web Report Designer by clicking on the `Next` button in the guide. You may skip the guide at any step by pressing the button `End Tour`. Pay attention to the Search functionality of the designer that lets you locate any report item, section, or property easily. ![The web report designer onboarding guide on the last step describing the global Search box.](images/web-designer-guide-search-box.png) @@ -71,13 +71,13 @@ Our next goal is to create a brand new report with the just configured Web Repor 1. Go to the main toolbar `Menu` and select `New Report`. The `Create Report` dialog opens and lets you: 1. Enter the `File Name`. Let's name the report `ProductSales`. - 1. Select the `Type`. Leave the `Type` to be `TRDP` standing for _Telerik Report Definition Packed_, the recommended Declarative [Report Definition]({%slug on-telerik-reporting%}#report-definition). + 1. Select the `Type`. Leave the `Type` to be `TRDP`, standing for _Telerik Report Definition Packed_, the recommended Declarative [Report Definition]({%slug on-telerik-reporting%}#report-definition). 1. Enter `Location`. Type `Demo` to place the report in the _Demo_ subfolder. 1. Click `Save` to apply the settings. ![The 'Create Report' dialog of the web designer with the above settings for our new report.](images/create-trdp-report-web-designer.png) -1. The new empty report should open in the designer with its default Page Header, Detail, and Page Footer sections. Let's delete the page sections by selecting them and pressing the `Delete` key from the keyboard. +1. The new empty report should open in the designer with its default Page Header, Detail, and Page Footer sections. Let's delete the page sections by selecting them and pressing the `Delete` key on the keyboard. 1. Next, we want to add a [Report Header]({%slug telerikreporting/designing-reports/report-structure/how-to/how-to-add-remove-report-header---footer-sections%}). Press `Ctrl+F` to focus the Search box, type `Report Header`, and press `Enter` key to focus the report section in the `Components` menu. Click the item to add the section to the report. ![Searching for the 'Report Header' and locating it in the web designer's 'Components' menu.](images/locate-report-header-component.png) @@ -89,9 +89,9 @@ Our next goal is to create a brand new report with the just configured Web Repor ![The 'Select file...' dialog of the web designer opened when adding a value for the PictureBox.](images/select-image-for-picturebox-web-designer.png) - 1. Select the `Images` folder and click the `Upload` button to upload the image. Click on the `Browse` button to find the image on your system and open it. Add the selected image by clicking on the `Upload` button. Now the image is in the Assets Manager and you may click `Save`. The value should be populated and the image should be displayed in the PictureBox. + 1. Select the `Images` folder and click the `Upload` button to upload the image. Click on the `Browse` button to find the image on your system and open it. Add the selected image by clicking on the `Upload` button. Now the image is in the Assets Manager, and you may click `Save`. The value should be populated, and the image should be displayed in the PictureBox. -1. Add title to the report. You may use the [TextBox]({%slug telerikreporting/designing-reports/report-structure/textbox%}) report item. +1. Add a title to the report. You may use the [TextBox]({%slug telerikreporting/designing-reports/report-structure/textbox%}) report item. 1. Search in the global search box of the designer and drag the item from the `Components` menu to the Report Header. 1. You may change the text inline. Double-click on the item to enter it and type `Sales by Category`. @@ -103,27 +103,27 @@ Our next goal is to create a brand new report with the just configured Web Repor 1. Our next step would be to add a [DataSource component]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/overview%}) to the Report. Let it be the [WebServiceDataSource]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/webservicedatasource-component/overview%}) fetching data from a remote source. 1. Search for the component and add it to the report. It opens the _Configure Web Service DataSource_ wizard. - 1. For `ServiceUrl` we will add the known URL to our demo site `https://demos.telerik.com/reporting/api/data/ProductSales.min`. It points to a reliable JSON data file. Leave the other options with their default values. + 1. For `ServiceUrl`, we will add the known URL to our demo site `https://demos.telerik.com/reporting/api/data/ProductSales.min`. It points to a reliable JSON data file. Leave the other options with their default values. ![The first page of the 'Configure WebServiceDataSource' wizard in the web designer.](images/configure-web-service-data-source-web-designer.png) 1. Skip the next page, where you may add request parameters, as we don't have any. - 1. Skip also the third page that asks whether in design-time you would like to use real or mocked data. We will use real data (the default setting). + 1. Skip also the third page that asks whether, in design-time, you would like to use real or mocked data. We will use real data (the default setting). 1. Preview the data on the next page and click `Finish`. ![The last page of the 'Configure WebServiceDataSource' wizard in the web designer shows the 'Preview data source results'.](images/preview-data-web-service-data-source-web-designer.png) - 1. The wizard closes and in the designer's `Explorer` tab you should see the new WebServiceDataSource component with its data fields listed. + 1. The wizard closes, and in the designer's `Explorer` tab, you should see the new WebServiceDataSource component with its data fields listed. 1. Next, lets add the [Graph]({%slug telerikreporting/designing-reports/report-structure/graph/overview%}) item that is going to show the sales data. - 1. Search for `Column` and drag the Column chart from the `Explorer` menu to the report Detail section. This will open a chart configurator to the right pane. + 1. Search for `Column` and drag the Column chart from the `Explorer` menu to the report Detail section. This will open a chart configurator in the right pane. 1. Select the WebServiceDataSource from the dropdown of the Graph DataSource property. The fields will be listed. ![Configuring the Column Chart in the web report designer.](images/configure-column-chart-web-designer.png) 1. Drag the `ProductCategory` field to the `Categories`. - 1. For the `Values` property use the `LineTotal` field. + 1. For the `Values` property, use the `LineTotal` field. 1. Click on `Create` to render the chart with real data and show it in the report. 1. Finally, style the column graph: @@ -132,14 +132,14 @@ Our next goal is to create a brand new report with the just configured Web Repor ![Styling the Column Chart in the web report designer.](images/style-column-chart-web-designer.png) -1. Preview the pixel-perfect report document by clicking on the designer `Preview` button at the top right corner. +1. Preview the pixel-perfect report document by clicking on the designer's `Preview` button at the top right corner. ## See Also * [Video tutorial 'Getting Started with the Web Report Designer: Part 1'](https://www.youtube.com/watch?v=L-utkcB8-5c) * [Video tutorial 'Getting Started with the Web Report Designer: Part 2'](https://www.youtube.com/watch?v=DXKlgq-MYIU) * [Implement a Common Master-Detail Report Scenario]({%slug telerikreporting/getting-started/web-designer/improving-basic-report%}) -* [Web Report Designer](%{slug telerikreporting/designing-reports/report-designer-tools/web-report-designer/overview%}) +* [Web Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/web-report-designer/overview%}) * [Setting up the Web Report Designer in .NET and .NET Core 3.1 applications]({%slug telerikreporting/designing-reports/report-designer-tools/web-report-designer/how-to-set-up-in-.net-5-and-.net-core-3.1-applications%}) * [Demo Page for Telerik Reporting](https://demos.telerik.com/reporting) * [Telerik Reporting Homepage](https://www.telerik.com/products/reporting) diff --git a/knowledge-base/before-2025.md b/knowledge-base/before-2025.md index ecdc5e2f7..f3ace1fdb 100644 --- a/knowledge-base/before-2025.md +++ b/knowledge-base/before-2025.md @@ -13,7 +13,7 @@ previous_url: /installation-trial-license-limitation Before Q2 2025, Telerik Reporting was distributed in two versions: Trial and Developer (commercial), each having its own assets. Starting with Q2 2025, Telerik Reporting comes in a unified installation package regardless of whether you have a developer (commercial) or a trial license. ->caution Starting with [Telerik Reporting version Q1 2025](https://www.telerik.com/blogs/license-key-files-telerik-kendo-ui-products-2025-update), you must activate the product through a [license key]({%slug setting-up-license-key%}) (trial or commercial). To upgrade from a Trial to a Developer (or commercial) license, purchase a license and then download a new license key, without re-installing the product. +> Starting with [Telerik Reporting version Q1 2025](https://www.telerik.com/blogs/license-key-files-telerik-kendo-ui-products-2025-update), you must activate the product through a [license key]({%slug setting-up-license-key%}) (trial or commercial). To upgrade from a Trial to a Developer (or commercial) license, purchase a license and then download a new license key, without re-installing the product. ## Trial Licenses diff --git a/knowledge-base/check-if-data-field-exists-before-using-it.md b/knowledge-base/check-if-data-field-exists-before-using-it.md index 7f335ba8f..4b85395e6 100644 --- a/knowledge-base/check-if-data-field-exists-before-using-it.md +++ b/knowledge-base/check-if-data-field-exists-before-using-it.md @@ -1,6 +1,6 @@ --- title: Check If Data Field Exists Before Using It -description: How to avoid Report error when data field does not exist +description: "Learn how to avoid Report errors when a data field does not exist." type: how-to page_title: Avoid Report error when no such data field slug: check-if-data-field-exists-before-using-it @@ -22,14 +22,14 @@ res_type: kb ## Description -In some scenarios, part of the fields used to design a report may not be available at runtime. This will cause an exception in -the report stating that the corresponding field is not defined in the current scope. The error message will be displayed in a red rectangle replacing the corresponding report item. The error rectangle cannot be customized and its size cannot be controlled. This may cause additional issues in report rendering as extra horizontal page breaks that may lead to report documents with more than the expected number of pages. + +In some scenarios, part of the fields used to design a report may not be available at runtime. This will cause an exception in the report stating that the corresponding field is not defined in the current scope. The error message will be displayed in a red rectangle, replacing the corresponding report item. The error rectangle cannot be customized, and its size cannot be controlled. This may cause additional issues in report rendering, as extra horizontal page breaks may lead to report documents with more than the expected number of pages. ## Solution -Create a [User Function]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/extending-expressions/user-functions%}) that returns the data field when it exists, and a default value when -the column is not available. Here is a sample implementation: -```CSharp +Create a [User Function]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/extending-expressions/user-functions%}) that returns the data field when it exists, and a default value when the column is not available. Here is a sample implementation: + +````CSharp public static object IfFieldDoesNotExist(Telerik.Reporting.Processing.IDataObject dataObject, string fieldName, object defaultValue) { object result; @@ -40,19 +40,15 @@ public static object IfFieldDoesNotExist(Telerik.Reporting.Processing.IDataObjec return defaultValue; } -``` -The function receives as arguments the [data object](/api/telerik.reporting.processing.processingelement#collapsible-Telerik_Reporting_Processing_ProcessingElement_DataObject) in the current -[data scope](,,/expressions-scope), the name of the field that is checked, and the default value that will be used when the field -does not exist in the data source. -The function can be used in the Report like: +```` -``` -=IfFieldDoesNotExist(ReportItem.DataObject, "FieldNameHere", DefaultValueHere) -``` +The function receives as arguments the [data object](/api/telerik.reporting.processing.processingelement#Telerik_Reporting_Processing_ProcessingElement_DataObject) in the current [data scope]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/expression-scope-%}), the name of the field that is checked, and the default value that will be used when the field does not exist in the data source. The function can be used in the Report like: -Details about the _ReportItem.DataObject_ can be found in -[How to use the ReportItem.DataObject property in expressions]({%slug telerikreporting/designing-reports/connecting-to-data/data-items/how-to-use-the-reportitem.dataobject-property-in-expressions%}) article. +`=IfFieldDoesNotExist(ReportItem.DataObject, "FieldNameHere", DefaultValueHere)` + +Details about the _ReportItem.DataObject_ can be found in [How to use the ReportItem.DataObject property in expressions]({%slug telerikreporting/designing-reports/connecting-to-data/data-items/how-to-use-the-reportitem.dataobject-property-in-expressions%}) article. ## See Also -[Error handling in Reports and Report Viewers](https://www.telerik.com/support/kb/reporting/details/error-handling-in-reports-and-report-viewers) -[Extending Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/configuration/extending-report-designer%}) + +* [Error handling in Reports and Report Viewers]({%slug error-handling-in-reports-and-report-viewers%}) +* [Extending Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/configuration/extending-report-designer%}) diff --git a/knowledge-base/command-injection-cve-2024-7840.md b/knowledge-base/command-injection-cve-2024-7840.md index 22fa47bcb..9698f58af 100644 --- a/knowledge-base/command-injection-cve-2024-7840.md +++ b/knowledge-base/command-injection-cve-2024-7840.md @@ -25,7 +25,7 @@ We have addressed the issue and the Progress® Telerik® team recommends perform | Current Version | Guidance | |-----------------|----------| -| 2024 Q3 (18.2.24.806) or earlier | Update to 2024 Q3 (18.2.24.924) ([update instructions](({%slug telerikreporting/upgrade/overview%}))) | +| 2024 Q3 (18.2.24.806) or earlier | Update to 2024 Q3 (18.2.24.924) ([update instructions]({%slug telerikreporting/upgrade/overview%})) | All customers who have a Telerik Reporting license can access the downloads here [Product Downloads | Your Account](https://www.telerik.com/account/downloads/product-download?product=REPORTING). diff --git a/knowledge-base/configure-the-stand-alone-report-designer-sqlite-data-provider.md b/knowledge-base/configure-the-stand-alone-report-designer-sqlite-data-provider.md index 825ff7858..bb6452dee 100644 --- a/knowledge-base/configure-the-stand-alone-report-designer-sqlite-data-provider.md +++ b/knowledge-base/configure-the-stand-alone-report-designer-sqlite-data-provider.md @@ -28,7 +28,7 @@ res_type: kb > Visit the updated [Integrating the SQLite Data Provider]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/sqldatasource-component/using-data-providers/using-sqlite-data-provider%}) article for a how-to on connecting to SQLite Databases. -Configuring the SQLite ADO.NET Provider for the Stand-alone Report Designer requires a few steps. If one is missed, the DataSource provider will not work in the Report Designer. Follow the below steps to get this working. +Configuring the SQLite ADO.NET Provider for the Stand-alone Report Designer requires a few steps. If one is missed, the DataSource provider will not work in the Report Designer. Follow the steps below to get this working. ## Solutions @@ -69,8 +69,8 @@ The Telerik Reporting directory will look like the following: **Step 2** Unpackage the zip with the binaries and copy the `System.Data.Sqlite.dll` file to the .NET Report Designer installation directory. -**Step 3** Download SQLite binaries built for `.NET Framework.4.X` from the [System.Data.Sqlite](http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki) page, for example [sqlite-netFx40-binary-x64-2010-1.0.117.0.zip](https://system.data.sqlite.org/downloads/1.0.117.0/sqlite-netFx40-binary-x64-2010-1.0.117.0.zip). Then unpackage the archive and copy the `SQLite.Interop.dll` assembly to the . NET Report Designer installation directory. - +**Step 3** Download SQLite binaries built for `.NET Framework.4.X` from the [System.Data.Sqlite](http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki) page. Then, unpackage the archive and copy the `SQLite.Interop.dll` assembly to the .NET Report Designer installation directory. + ![sqlite net designer install folder](resources/sqlite_net_designer_install.png) The .NET 6 Standalone Report Designer will automatically locate and load the SQLite assemblies, thus the data provider will appear in the SqlDataSource wizard dropdown. There is no need to edit the configuration of the .NET Report Designer - [Differences between the .NET and .NET Framework designers' functionality]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview%}#differences-between-the-net-and-net-framework-designers-functionality) diff --git a/knowledge-base/deserialization-vulnerability-cve-2024-4200.md b/knowledge-base/deserialization-vulnerability-cve-2024-4200.md index 28473e4d9..ff6757f04 100644 --- a/knowledge-base/deserialization-vulnerability-cve-2024-4200.md +++ b/knowledge-base/deserialization-vulnerability-cve-2024-4200.md @@ -23,11 +23,11 @@ Local code execution can occur when the Telerik Reporting engine deserializes un ## Solution -Updating to at least version Reporting 2024 Q2 (18.1.24.514) is the only way to remove this vulnerability. We have addressed the vulnerability and the Progress Telerik team strongly recommends performing an upgrade to the latest version listed in the table below. +Updating to at least version Reporting 2024 Q2 (18.1.24.514) is the only way to remove this vulnerability. We have addressed the vulnerability, and the Progress Telerik team strongly recommends performing an upgrade to the latest version listed in the table below. | Current Version | Guidance | |-----------------|----------| -| 2024 Q1 (18.0.24.305) or earlier | Update to 2024 Q2 (18.1.24.2.514) ([update instructions](({%slug telerikreporting/upgrade/overview%}))) | +| 2024 Q1 (18.0.24.305) or earlier | Update to 2024 Q2 (18.1.24.2.514) ([update instructions]({%slug telerikreporting/upgrade/overview%})) | All customers who have a Telerik Reporting license can access the downloads here [Product Downloads | Your Account](https://www.telerik.com/account/downloads/product-download?product=REPORTING). diff --git a/knowledge-base/export-of-blazor-native-viewer-in-telerik-window-not-working.md b/knowledge-base/export-of-blazor-native-viewer-in-telerik-window-not-working.md index 020b367b1..7b4f56b01 100644 --- a/knowledge-base/export-of-blazor-native-viewer-in-telerik-window-not-working.md +++ b/knowledge-base/export-of-blazor-native-viewer-in-telerik-window-not-working.md @@ -4,8 +4,6 @@ description: "Learn how to visualize the export menu of the Blazor Native Report type: how-to page_title: The Export menu of the Blazor Native Report Viewer does not show when the viewer is in TelerikWindow slug: export-of-blazor-native-viewer-in-telerik-window-not-working -position: -tags: ticketid: 1592541 res_type: kb --- @@ -30,7 +28,7 @@ res_type: kb Clicking on the `Export` button from the menu of the [Native Blazor Report Viewer]({%slug telerikreporting/embedding-reports/display-reports-in-applications/web-application/native-blazor-report-viewer/overview%}) when hosted in the Telerik UI for Blazor [TelerikWindow](https://docs.telerik.com/blazor-ui/components/window/overview) modal window component doesn't display the expected available export formats. The problem is in the [ContextMenu](https://docs.telerik.com/blazor-ui/components/contextmenu/overview) that is opened when clicking on the `Export` button. It is hidden behind the modal window. -This is a known bug in the Telerik UI for Blazor - [The ContextMenu is hidden behind the Modal Window #2554](https://github.com/telerik/blazor/issues/2554). Solving this issue should fix the problem also in the viewer. +This is a known bug in the Telerik UI for Blazor - [The ContextMenu is hidden behind the Modal Window #2554](https://feedback.telerik.com/blazor/1520526-the-contextmenu-is-hidden-behind-the-modal-window). Solving this issue should also fix the problem in the viewer. ## Suggested Workarounds @@ -46,6 +44,6 @@ Increase the Z-index of the Telerik UI for Blazor ContextMenu that lists the ava ## See Also -* [The ContextMenu is hidden behind the Modal Window #2554](https://github.com/telerik/blazor/issues/2554) +* [The ContextMenu is hidden behind the Modal Window #2554](https://feedback.telerik.com/blazor/1520526-the-contextmenu-is-hidden-behind-the-modal-window) * [Native Blazor Report Viewer]({%slug telerikreporting/embedding-reports/display-reports-in-applications/web-application/native-blazor-report-viewer/overview%}) * [TelerikWindow](https://docs.telerik.com/blazor-ui/components/window/overview) diff --git a/knowledge-base/extract-inline-images-picturebox-telerik-reporting.md b/knowledge-base/extract-inline-images-picturebox-telerik-reporting.md index 15de84539..d7cef0106 100644 --- a/knowledge-base/extract-inline-images-picturebox-telerik-reporting.md +++ b/knowledge-base/extract-inline-images-picturebox-telerik-reporting.md @@ -4,7 +4,7 @@ description: "Learn how to retrieve and save inline images embedded in a Picture type: how-to page_title: How to Extract and Save Inline Images from a PictureBox in Telerik Reporting TRDP Templates slug: extract-inline-images-picturebox-telerik-reporting -tags: progress® telerik® reporting, report, picturebox, image, extract, save, trdp +tags: progress, telerik, reporting, report, picturebox, image, extract, save, trdp res_type: kb ticketid: 1674786 --- @@ -42,6 +42,5 @@ To extract and save the original image embedded in a PictureBox within a Telerik ## See Also -- [Telerik Reporting Documentation](https://docs.telerik.com/reporting/overview) -- [Managing Report Resources](https://docs.telerik.com/reporting/designing-reports-managing-report-resources) -- [How to Add a PictureBox to a Report](https://docs.telerik.com/reporting/picturebox) +- [Telerik Reporting Documentation]({%slug telerikreporting/welcome-to-telerik-reporting!%}) +- [How to Add a PictureBox to a Report]({%slug telerikreporting/designing-reports/report-structure/picturebox%}) diff --git a/knowledge-base/font-is-missing-in-report-designers.md b/knowledge-base/font-is-missing-in-report-designers.md index 1e87d4218..95d59c338 100644 --- a/knowledge-base/font-is-missing-in-report-designers.md +++ b/knowledge-base/font-is-missing-in-report-designers.md @@ -36,7 +36,7 @@ In this article, we will explain why a font may be missing in the Report Designe The Telerik Reporting engine uses the **GDI+** library and depends on the fonts that **GDI+** supports. -In this line of thought, .NET supports **only** TrueType fonts. Thus, you can not use **OpenType** fonts with Telerik Reporting. If applicable. you can convert the OpenType font to **TrueType** using a [free online converter](http://www.freefontconverter.com/). +In this line of thought, .NET supports **only** TrueType fonts. Thus, you can not use **OpenType** fonts with Telerik Reporting. If applicable. you can convert the OpenType font to **TrueType** using a [free online converter](https://www.fontconverter.org/). > If the font is TrueType, check if the font is installed in **%windir%\fonts**. diff --git a/knowledge-base/hide-gridlines-crosstab-table-telerik-reporting.md b/knowledge-base/hide-gridlines-crosstab-table-telerik-reporting.md index ef3379986..be1e4273b 100644 --- a/knowledge-base/hide-gridlines-crosstab-table-telerik-reporting.md +++ b/knowledge-base/hide-gridlines-crosstab-table-telerik-reporting.md @@ -30,7 +30,7 @@ The next sections discuss the particular Binding Expression for the top border s ### One Table Group -Let's start with the simplest case when there is only one group in the crosstab/table. Remember that each data item has also a 'detail' group that is instantiated for each data record. That said, in this case, we have two groups. Here is the expression that may be used in both group cells to set the border: +Let's start with the simplest case when there is only one group in the crosstab/table. Remember that each data item also has a 'detail' group that is instantiated for each data record. That said, in this case, we have two groups. Here is the expression that may be used in both group cells to set the border: ````Expression = Previous(Fields.group) = Fields.group ? @@ -79,7 +79,7 @@ The next steps let you keep each group on the same page when the table occupies * Set the right-most cells' `Right Border Style` to `Solid` so that the Table recovers its right borders. * Set the left-most cells' `Left Border Style` to `Solid` so that the Table recovers its left borders. -The above steps let each group be rendered together on the same page and have proper borders, excluding the last one on the page. We need also to add a bottom border to the last group. +The above steps let each group be rendered together on the same page and have proper borders, excluding the last one on the page. We also need to add a bottom border to the last group. One easy approach is through the following steps that are implemented in the sample report [ThreeGroupsPageBreak.trdx](https://github.com/telerik/reporting-samples/blob/master/Sample%20Reports/TableGroupBorders/ThreeGroupsPageBreak.trdx): @@ -87,9 +87,9 @@ One easy approach is through the following steps that are implemented in the sam * Select the cells of the new row and set all outer borders to `Solid`, and all the rest to `None`. * Minimize the new row's height as it will be used only to display borders and won't show any data. -The above solution will result in a small whitespace below each group content, as the table row has a minimal allowed height. +The above solution will result in a small whitespace below each group of content, as the table row has a minimal allowed height. -An alternative workaround for the bottom table border when wrapping the table on a new page would be to use the `Last` [aggregate function](slug telerikreporting/designing-reports/connecting-to-data/expressions/expressions-reference/functions/aggregate-functions) in the Binding for setting the Border Style. If the current value is equal to the Last for the group, we may draw the bottom border. This will work only if there is a data field with unique values. Otherwise, the comparison with the Last value may return True for some of the inner records and draw an unwanted border in the middle of the group. +An alternative workaround for the bottom table border when wrapping the table on a new page would be to use the `Last` [aggregate function]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/expressions-reference/functions/aggregate-functions%}) in the Binding for setting the Border Style. If the current value is equal to the Last for the group, we may draw the bottom border. This will work only if there is a data field with unique values. Otherwise, the comparison with the Last value may return True for some of the inner records and draw an unwanted border in the middle of the group. ## Sample Reports diff --git a/knowledge-base/how-to-customize-web-service-data-source-url.md b/knowledge-base/how-to-customize-web-service-data-source-url.md index 53de43233..f0c76acc0 100644 --- a/knowledge-base/how-to-customize-web-service-data-source-url.md +++ b/knowledge-base/how-to-customize-web-service-data-source-url.md @@ -1,16 +1,15 @@ --- -title: How to customize WebServiceDataSource URL -description: Modify WebServiceDataSource URL dynamically +title: How to Customize WebServiceDataSource URL +description: "Learn how to modify WebServiceDataSource URL dynamically." type: how-to -page_title: Provide WebServiceDataSource URL as inline parameter +page_title: Provide WebServiceDataSource URL as an inline parameter slug: how-to-customize-web-service-data-source-url -position: -tags: ticketid: 1345801 res_type: kb --- ## Environment + @@ -20,15 +19,18 @@ res_type: kb ## Description -Sometimes it is necessary to modify the WebServiceDataSource URL dynamically, for example depending on the environment (i.e. test or production). + +Sometimes it is necessary to modify the WebServiceDataSource URL dynamically, for example, depending on the environment (i.e., test or production). ## Solution + 1. The **Service Url** property of the _WebServiceDataSource_ should be set as an inline parameter **@Url**, i.e. in _Configure data retrieval_ dialog of the [WebServiceDataSource Wizard]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/tools/data-source-wizards/webservicedatasource-wizard%}): _Service Url:_| __@Url__ ---|--- -2. The value of _@Url_ should be provided as an [Expression]({% slug telerikreporting/designing-reports/connecting-to-data/expressions/overview %}) (i.e. taken from a Report Parameter) so that its value to be evaluated run time - in _Configure request parameters_ dialog of the Wizard : - _Name_|_Type_|_Value_|_Design-Time Value_ - ---|---|---|--- - @Url|__Inline__|= Parameters.Url.Value|https://www.googleapis.com/books/v1/volumes +1. The value of _@Url_ should be provided as an [Expression]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/overview%}) (i.e., taken from a Report Parameter) so that its value can be evaluated at run time in the _Configure request parameters_ dialog of the Wizard: + + _Name_|_Type_|_Value_|_Design-Time Value_ + ---|---|---|--- + @Url|__Inline__|= Parameters.Url.Value|_A valid URL to a Web Service_ diff --git a/knowledge-base/how-to-determine-effective-visibility-of-parameters-area.md b/knowledge-base/how-to-determine-effective-visibility-of-parameters-area.md index 57e873b1c..378748ad0 100644 --- a/knowledge-base/how-to-determine-effective-visibility-of-parameters-area.md +++ b/knowledge-base/how-to-determine-effective-visibility-of-parameters-area.md @@ -11,6 +11,7 @@ res_type: kb --- ## Environment +
Product
@@ -24,14 +25,17 @@ res_type: kb
- ## Description -In the Angular Report Viewer component, one may successfully control the visibility of the parameter area with the means of the _parametersAreaVisible_ [option]({% slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/angular-report-viewer/angular-report-viewer-overview %}-api-options). However, it cannot be used to determine what is the current state of the parameters area visibility that may have changed due to user interaction with the viewer. + +In the Angular Report Viewer component, one may successfully control the visibility of the parameter area with the means of the _parametersAreaVisible_ [option]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/angular-report-viewer/api-reference/options%}#available-options). However, it cannot be used to determine the current state of the parameters area visibility that may have changed due to user interaction with the viewer. ## Suggested Workarounds -The _parametersAreaVisible_ as any other option of the viewer specifies only the initial/default value of the corresponding property, and its value is not updated afterward. That's why it is not possible to take the state of the parameters area visibility from it. -As a workaround, you may use _jQuery_ to get the html element of the parameters area and check whether its width is 0. If so, the parameters area is hidden. This may be done, for example, on the _updateUi_ [event]({% slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/angular-report-viewer/angular-report-viewer-overview %}-api-events). Here is also the code for selecting the area and taking its width: -```JavaScript +The _parametersAreaVisible_, as any other option of the viewer, specifies only the initial/default value of the corresponding property, and its value is not updated afterward. That's why it is not possible to take the state of the parameters area visibility from it. + +As a workaround, you may use _jQuery_ to get the html element of the parameters area and check whether its width is 0. If so, the parameters' area is hidden. This may be done, for example, on the _updateUi_ [event]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/angular-report-viewer/api-reference/events%}). Here is also the code for selecting the area and taking its width: + +````JavaScript $(".trv-parameters-area").width() -``` +```` + diff --git a/knowledge-base/how-to-remove-trial-message.md b/knowledge-base/how-to-remove-trial-message.md index b06f75a54..2cedb772a 100644 --- a/knowledge-base/how-to-remove-trial-message.md +++ b/knowledge-base/how-to-remove-trial-message.md @@ -28,7 +28,7 @@ res_type: kb This tutorial explains in detail how to upgrade your Telerik [Trial]({%slug telerikreporting/licensing%}) to a Licensed version of [Telerik Reporting](https://www.telerik.com/account/product-download?product=REPORTING). ->caution Starting with [Telerik Reporting version Q1 2025](https://www.telerik.com/blogs/license-key-files-telerik-kendo-ui-products-2025-update), you must activate the product through a [license key]({%slug setting-up-license-key%}) (trial or commercial). To upgrade from a Trial to a Developer (or commercial) license, purchase a license and then download a new license key, without re-installing the product. +> Starting with [Telerik Reporting version Q1 2025](https://www.telerik.com/blogs/license-key-files-telerik-kendo-ui-products-2025-update), you must activate the product through a [license key]({%slug setting-up-license-key%}) (trial or commercial). To upgrade from a Trial to a Developer (or commercial) license, purchase a license and then download a new license key, without re-installing the product. Let's start with having a trial version installed on your machine and a project that uses the trial version. Access to the Trial version of product files in the Downloads section of your Telerik account: diff --git a/knowledge-base/how-to-set-report-documentname-as-web-page-document-title.md b/knowledge-base/how-to-set-report-documentname-as-web-page-document-title.md index 10ee508ce..3368f2bff 100644 --- a/knowledge-base/how-to-set-report-documentname-as-web-page-document-title.md +++ b/knowledge-base/how-to-set-report-documentname-as-web-page-document-title.md @@ -22,13 +22,13 @@ res_type: kb ## Description -The article explains how to set the [Document Title](https://developer.mozilla.org/en-US/docs/Web/API/Document/title) that will appear in the browser tab of the Web Page hosting the [HHTML5 Report Viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/overview%}) or any of its wrappers to the `DocumentName` of the Report. +The article explains how to set the [Document Title](https://developer.mozilla.org/en-US/docs/Web/API/Document/title) that will appear in the browser tab of the Web Page hosting the [HTML5 Report Viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/overview%}) or any of its wrappers to the `DocumentName` of the Report. ## Solution -1. If the Report already has [Document Map]({%slug telerikreporting/designing-reports/adding-interactivity-to-reports/document-map/overview%}) go to the next step. Otherwise, in the report definition set the [DocumentMapText](/api/telerik.reporting.reportitembase#collapsible-Telerik_Reporting_ReportItemBase_DocumentMapText) property of a report item (e.g. _TextBox_) to a valid value. The `DocumentMapText` will introduce `Document Map` in the Report. This way the `DocumentName` of the Report would be included in the `bookmarkNodes` collection of the `args` object of the [renderingEnd]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/api-reference/reportviewer/events/renderingend(e,-args)%}) event of the viewer. +1. If the Report already has [Document Map]({%slug telerikreporting/designing-reports/adding-interactivity-to-reports/document-map/overview%}) go to the next step. Otherwise, in the report definition, set the [DocumentMapText](/api/telerik.reporting.reportitembase#collapsible-Telerik_Reporting_ReportItemBase_DocumentMapText) property of a report item (e.g., _TextBox_) to a valid value. The `DocumentMapText` will introduce `Document Map` in the Report. This way, the `DocumentName` of the Report would be included in the `bookmarkNodes` collection of the `args` object of the [renderingEnd]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/api-reference/reportviewer/events/renderingend(e,-args)%}) event of the viewer. -1. In the event handler of `renderingEnd` the name of the Report can be taken from `args.bookmarkNodes` and assigned to the title of the document: +1. In the event handler of `renderingEnd`, the name of the Report can be taken from `args.bookmarkNodes` and assigned to the title of the document: ````JavaScript $("#reportViewer1") @@ -44,7 +44,7 @@ $("#reportViewer1") ```` -1. The `Document Map` may be hidden in the viewer's initialization by setting the `documentMapVisible` property to `false` - [Initializing the HTML5 Report Viewer]({&slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/api-reference/report-viewer-initialization%}). +1. The `Document Map` may be hidden in the viewer's initialization by setting the `documentMapVisible` property to `false` - [Initializing the HTML5 Report Viewer]({%&slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/api-reference/report-viewer-initialization%}). ## Demo Project diff --git a/knowledge-base/insecure-expression-evaluation-cve-2024-8048.md b/knowledge-base/insecure-expression-evaluation-cve-2024-8048.md index 6bd811ceb..a92cbf9c0 100644 --- a/knowledge-base/insecure-expression-evaluation-cve-2024-8048.md +++ b/knowledge-base/insecure-expression-evaluation-cve-2024-8048.md @@ -25,7 +25,7 @@ We have addressed the issue and the Progress® Telerik® team recommends perform | Current Version | Guidance | |-----------------|----------| -| 2024 Q3 (18.2.24.806) or earlier | Update to 2024 Q3 (18.2.24.924) ([update instructions](({%slug telerikreporting/upgrade/overview%}))) | +| 2024 Q3 (18.2.24.806) or earlier | Update to 2024 Q3 (18.2.24.924) ([update instructions]({%slug telerikreporting/upgrade/overview%})) | All customers who have a Telerik Reporting license can access the downloads here [Product Downloads | Your Account](https://www.telerik.com/account/downloads/product-download?product=REPORTING). @@ -46,4 +46,4 @@ All customers who have a Telerik Reporting license can access the downloads here In Progress® Telerik® Reporting versions prior to 2024 Q3 (18.2.24.924), a code execution attack is possible using object injection via insecure expression evaluation. -Discoverer Credit: Markus Wulftange with CODE WHITE GmbH. \ No newline at end of file +Discoverer Credit: Markus Wulftange with CODE WHITE GmbH. diff --git a/knowledge-base/insecure-type-resolution-cve-2024-8014.md b/knowledge-base/insecure-type-resolution-cve-2024-8014.md index 5b08dd4b8..dc12ed762 100644 --- a/knowledge-base/insecure-type-resolution-cve-2024-8014.md +++ b/knowledge-base/insecure-type-resolution-cve-2024-8014.md @@ -25,7 +25,7 @@ We have addressed the issue and the Progress® Telerik® team recommends perform | Current Version | Guidance | |-----------------|----------| -| 2024 Q3 (18.2.24.806) or earlier | Update to 2024 Q3 (18.2.24.924) ([update instructions](({%slug telerikreporting/upgrade/overview%}))) | +| 2024 Q3 (18.2.24.806) or earlier | Update to 2024 Q3 (18.2.24.924) ([update instructions]({%slug telerikreporting/upgrade/overview%})) | All customers who have a Telerik Reporting license can access the downloads here [Product Downloads | Your Account](https://www.telerik.com/account/downloads/product-download?product=REPORTING). @@ -45,4 +45,4 @@ All customers who have a Telerik Reporting license can access the downloads here In Progress® Telerik® Reporting versions prior to 2024 Q3 (18.2.24.924), a code execution attack is possible through object injection via an insecure type resolution vulnerability. -Discoverer Credit: Markus Wulftange with CODE WHITE GmbH \ No newline at end of file +Discoverer Credit: Markus Wulftange with CODE WHITE GmbH diff --git a/knowledge-base/instantiation-vulnerability-cve-2024-4202.md b/knowledge-base/instantiation-vulnerability-cve-2024-4202.md index 096a8df72..23c9072b1 100644 --- a/knowledge-base/instantiation-vulnerability-cve-2024-4202.md +++ b/knowledge-base/instantiation-vulnerability-cve-2024-4202.md @@ -27,7 +27,7 @@ Updating to at least version Reporting 2024 Q2 (18.1.24.514) is the only way to | Current Version | Guidance | |-----------------|----------| -| 18.0.24.305 (or earlier) | Update to 18.1.24.514 ([update instructions](({%slug telerikreporting/upgrade/overview%}))) | +| 18.0.24.305 (or earlier) | Update to 18.1.24.514 ([update instructions]({%slug telerikreporting/upgrade/overview%})) | All customers who have a Telerik Reporting license can access the downloads here [Product Downloads | Your Account](https://www.telerik.com/account/downloads/product-download?product=REPORTING). diff --git a/knowledge-base/postgres-stored-functions-in-sqldatasource-wizard.md b/knowledge-base/postgres-stored-functions-in-sqldatasource-wizard.md index 2a8689b35..58fec71ef 100644 --- a/knowledge-base/postgres-stored-functions-in-sqldatasource-wizard.md +++ b/knowledge-base/postgres-stored-functions-in-sqldatasource-wizard.md @@ -1,8 +1,8 @@ --- -title: Handling PostgreSQL Stored functions in Report Designer's SqlDataSource wizard -description: When using PostgreSQL with NpgSql provider the Stored procedure dropdown is not populating in Report Designer's SqlDataSource wizard. When using ODBC provider the functions will be listed, but the number of their arguments may be incorrect. +title: Handling PostgreSQL Stored functions in the Report Designer's SqlDataSource wizard +description: When using PostgreSQL with the NpgSql provider, the Stored procedure dropdown is not populating in the Report Designer's SqlDataSource wizard. When using the ODBC provider, the functions will be listed, but the number of their arguments may be incorrect. type: troubleshooting, how-to -page_title: How to handle PostgreSQL Stored functions in Report designer's SqlDataSource wizard +page_title: How to handle PostgreSQL Stored functions in the Report Designer's SqlDataSource wizard slug: postgres-stored-functions-in-sqldatasource-wizard position: tags: @@ -20,16 +20,16 @@ res_type: kb ## Description -In PostgreSQL prior to version 11 there are Stored functions. Stored Procedures have been introduced with version 11. +In PostgreSQL before version 11, there are Stored functions. Stored Procedures have been introduced with version 11. -1. When using ODBC provider for PostgreSQL with Stored functions, the Stored Procedure drop-down menu of the Report Designer's [SqlDataSource wizard]({% slug telerikreporting/designing-reports/connecting-to-data/data-source-components/sqldatasource-component/overview %}-wizard) is populated, but the returned scalar values or result set columns are included in the stored procedure's input arguments and will be listed as Stored Procedure arguments along with the real arguments, and the Stored function will not be correctly discovered, resulting in an exception. +1. When using the ODBC provider for PostgreSQL with Stored functions, the Stored Procedure drop-down menu of the Report Designer's [SqlDataSource wizard]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/tools/data-source-wizards/sqldatasource-wizard/overview%}) is populated, but the returned scalar values or result set columns are included in the stored procedure's input arguments and will be listed as Stored Procedure arguments along with the real arguments, and the Stored function will not be correctly discovered, resulting in an exception. -2. When using NpgSql provider the Report Designer's SqlDataSource wizard does not list the PostgreSQL Stored functions in the Stored Procedures drop-down menu. The issue applies to PostgreSQL prior to version 11. +2. When using the NpgSql provider, the Report Designer's SqlDataSource wizard does not list the PostgreSQL Stored functions in the Stored Procedures drop-down menu. The issue applies to PostgreSQL before version 11. ## Solution -1. In our implementation for ODBC providers we use the [DbCommandBuilder](https://docs.microsoft.com/en-us/dotnet/api/system.data.common.dbcommandbuilder?view=netframework-4.7.2) _DeriveParameters_ method (it is non-public and we access it with reflection) that returns all the actual function parameters, but also the Table columns returned by the query as collection (or single value) of [OdbcParameter](https://docs.microsoft.com/en-us/dotnet/api/system.data.odbc.odbcparameter?view=netframework-4.7.2) class with their property [Direction](https://docs.microsoft.com/en-us/dotnet/api/system.data.odbc.odbcparameter.direction?view=netframework-4.7.2) set to _Input_. Therefore, in our code, we create inputs for all (i.e. actual parameters as well as returned columns), and the stored procedure/function is passed and searched for by the provider with an incorrect number of parameters. -The workaround is to use an ADO.NET provider (for example NpgSql - see below). +1. In our implementation for ODBC providers we use the [DbCommandBuilder](https://docs.microsoft.com/en-us/dotnet/api/system.data.common.dbcommandbuilder?view=netframework-4.7.2) _DeriveParameters_ method (it is non-public and we access it with reflection) that returns all the actual function parameters, but also the Table columns returned by the query as collection (or single value) of [OdbcParameter](https://docs.microsoft.com/en-us/dotnet/api/system.data.odbc.odbcparameter?view=netframework-4.7.2) class with their property [Direction](https://docs.microsoft.com/en-us/dotnet/api/system.data.odbc.odbcparameter.direction?view=netframework-4.7.2) set to _Input_. Therefore, in our code, we create inputs for all (i.e., actual parameters as well as returned columns), and the stored procedure/function is passed and searched for by the provider with an incorrect number of parameters. +The workaround is to use an ADO.NET provider (for example, NpgSql - see below). 2. With the NpgSql provider, the Report Designer's SqlDataSource wizard does not list the PostgreSQL Stored functions in the Stored Procedures drop-down menu. However, when the function is manually typed, it will be correctly discovered and executed. After recognizing the function, the SqlDataSource wizard populates the Query parameter successfully in the next window. -The [NpgSql ADO.NET provider](https://www.npgsql.org/) can recognize the Stored functions. However, the wizard does not list the stored functions, because they are not provided in the schema information we request and therefore, the drop-down menu is not populated. +The [NpgSql ADO.NET provider](https://www.npgsql.org/) can recognize the Stored functions. However, the wizard does not list the stored functions because they are not provided in the schema information we request, and therefore, the drop-down menu is not populated. diff --git a/knowledge-base/print-error-chrome.md b/knowledge-base/print-error-chrome.md index 00ad93167..04f7a7552 100644 --- a/knowledge-base/print-error-chrome.md +++ b/knowledge-base/print-error-chrome.md @@ -1,16 +1,16 @@ --- title: Print dialog doesn't open in Google Chrome 77.0.3865.75 -description: Since the Google Chrome update to version 77.0.3865.75 the print functionality in the web-based viewers doesn't work +description: Since the Google Chrome update to version 77.0.3865.75, the print functionality in the web-based viewers doesn't work type: troubleshooting page_title: Print functionality does not work in Google Chrome 77.0.3865.75 slug: print-error-chrome -position: tags: HTML5Viewer, MVCReportViewer, WebFormsViewer, AngularViewer ticketid: 1429178 res_type: kb --- ## Environment + @@ -24,21 +24,22 @@ res_type: kb ## Description + After the Google Chrome update to version 77.0.3865.75, the print dialog doesn't open. -The printing functionality of all web viewers is based on PDF rendering and invoking the browsers PDF plug-in printing functionality. Note that for security reasons an application that is running in a browser cannot access directly the machine resources, e.g. printers. These are technical restrictions imposed by the browser and beyond the Telerik Reporting control. -Additionally, Google Chrome has also an available public thread on the topic: [Chrome 77, pdf auto print dialog](https://support.google.com/chrome/thread/14107571?hl=en). +The printing functionality of all web viewers is based on PDF rendering and invoking the browser's PDF plug-in printing functionality. Note that for security reasons, an application that is running in a browser cannot access the machine resources directly, e.g., printers. These are technical restrictions imposed by the browser and beyond the Telerik Reporting control. ## Solution -The issue is resolved in the [R3 2019](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-r3-2019-13-2-19-918) release where the print button of the HTML5 Report Viewer renders the report for print purposes and opens it in a new browser tab. The auto-print script is still embedded in the document, but Google Chrome will wait for user interaction in order to show its print dialog. +The issue is resolved in the [R3 2019](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-r3-2019-13-2-19-918) release, where the print button of the HTML5 Report Viewer renders the report for print purposes and opens it in a new browser tab. The auto-print script is still embedded in the document, but Google Chrome will wait for user interaction in order to show its print dialog. ## Workaround for the HTML5-based Report Viewers -This workaround was proposed by one of our users- check the post from **Thanh** in [Print Dialog doesn't appear in Google Chrome 77.0.3865.75](https://feedback.telerik.com/reporting/1429337-print-dialog-doesn-t-appear-in-google-chrome-77-0-3865-75) thread. It allows you to trigger the print dialog on **Print** click. Our user **Naumand** updated it, so the same functionality is achieved in Firefox. + +This workaround was proposed by one of our users- check the post from **Thanh** in [Print Dialog doesn't appear in Google Chrome 77.0.3865.75](https://feedback.telerik.com/reporting/1429337-print-dialog-doesn-t-appear-in-google-chrome-77-0-3865-75) thread. It allows you to trigger the print dialog on the **Print** click. Our user **Naumand** updated it, so the same functionality is achieved in Firefox. Here are the required steps: -1) Add a reference to the [Print.js](https://printjs.crabbly.com/) third party library in the viewer's page (above the reference to the viewer's JavaScript file). -2) Copy the **telerikReportViewer-x.x.x.x.js** file locally and refer it in the page from the local source. For example, if the viewer is copied to the folder _"(base application folder)/ReportViewer"_ the references may look like: +1) Add a reference to the [Print.js](https://printjs.crabbly.com/) third-party library in the viewer's page (above the reference to the viewer's JavaScript file). +2) Copy the **telerikReportViewer-x.x.x.x.js** file locally and refer to it in the page from the local source. For example, if the viewer is copied to the folder _"(base application folder)/ReportViewer"_ the references may look like: -```JavaScript +````JavaScript ... @@ -46,19 +47,19 @@ Here are the required steps: ... -``` +```` 3) Modify the code of the **telerikReportViewer-x.x.x.x.js** file - function **printDesktop(src)**. Its original implementation is: -```JavaScript +````JavaScript function printDesktop(src) { window.open(src, "_blank"); } -``` +```` Change it to: -```JavaScript +````JavaScript trv.printManager = function () { var iframe; function printDesktop(src) { @@ -73,14 +74,15 @@ trv.printManager = function () { document.body.appendChild(iframe); } } -``` +```` ## Workaround 2 for the HTML5-based Report Viewers + Set the **FORCE_PDF_FILE** [printMode]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/api-reference/telerikreportviewer-namespace/printmodes%}) option of the report viewer, the widget will always export the report document to a PDF file with the special print script. For more information, check [Printing Reports]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/printing-reports%}) article. -For example in the [HTML5 Report viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/overview%}), you need to add the following line in the initialization of the viewer: +For example, in the [HTML5 Report viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/overview%}), you need to add the following line in the initialization of the viewer: -```JavaScript +````JavaScript $("#reportViewer1") .telerik_ReportViewer({ serviceUrl: "/api/reports", @@ -88,14 +90,15 @@ $("#reportViewer1") printMode: telerikReportViewer.PrintModes.FORCE_PDF_FILE }, ... -``` +```` -Note that this setting will not open the Print Dialog automatically but it will trigger downloading the PDF file. +Note that this setting will not open the Print Dialog automatically, but it will trigger downloading the PDF file. ## Workaround for the obsolete ASP.NET Web Forms Report Viewer -This workaround was also provided by one of our user **Michael** in the Feedback portal post. Here the **ReportViewer.prototype.PrintReport** is overriden: -```JavaScript +This workaround was also provided by one of our users, **Michael**, in the Feedback portal post. Here the **ReportViewer.prototype.PrintReport** is overridden: + +````JavaScript
-``` +```` + diff --git a/knowledge-base/reports-with-continuouspaper-or-custom-paperkind-cut-on-some-printers.md b/knowledge-base/reports-with-continuouspaper-or-custom-paperkind-cut-on-some-printers.md index 4a03b4d93..79432be62 100644 --- a/knowledge-base/reports-with-continuouspaper-or-custom-paperkind-cut-on-some-printers.md +++ b/knowledge-base/reports-with-continuouspaper-or-custom-paperkind-cut-on-some-printers.md @@ -23,7 +23,7 @@ res_type: kb ## Description -When the report is longer than specific height, some printers, mostly label ones, for example, "EPSON TM-U220 Receipt", just stop printing, ignoring the remaining part of the report document. They print as expected when the printed reports are short though. +When the report is longer than a specific height, some printers, mostly label ones, for example, "EPSON TM-U220 Receipt", just stop printing, ignoring the remaining part of the report document. They print as expected when the printed reports are short, though. Changing the `PaperSize` > `Height` or `ContinuousPaper` from the report definition [PageSettings](/api/telerik.reporting.drawing.pagesettings) doesn't help. @@ -31,18 +31,18 @@ Changing the `PaperSize` > `Height` or `ContinuousPaper` from the report definit The Reporting engine delegates the printing entirely to the [System.Drawing.Printing](https://learn.microsoft.com/en-us/dotnet/api/system.drawing.printing?view=netframework-4.8) namespace. If the Microsoft functionality supports the particular printer, Telerik Reporting also does to the same extent. -There are many printers that support only limited paper sizes. This may be due to hardware or driver limitations. For example, the article [Instruction on how to set up the printer to print a bill which is longer than an A4 paper via EPSON TM-U220B](https://gettingstarted.cukcuk.com/huong_dan_thiet_lap_de_in_duoc_hoa_don_co_do_dai_lon_hon_trang_giay_a4_tren_may_in_epson_tmu220b.htm) explains that "When printing a bill with EPSON TM-U220B, it only prints to the length of 297 mm (equivalent to an A4 paper). The cause may be that driver of EPSON TM-U220B does not support the length of more than 297mm". +Many printers support only limited paper sizes. This may be due to hardware or driver limitations. For example, the article [Instruction on how to set up the printer to print a bill which is longer than an A4 paper via EPSON TM-U220B](https://helpv2.cukcuk.com/en/kb/instruction-on-how-to-set-up-the-printer-to-print-a-bill-which-is-longer-than-an-a4-paper-via-epson-tm-u220b/) explains that "When printing a bill with EPSON TM-U220B, it only prints to the length of 297 mm (equivalent to an A4 paper). The cause may be that the driver of EPSON TM-U220B does not support a length of more than 297mm". As an example, when printing a larger report from the [Standalone Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview%}) to the `Microsoft PDF Printer` with either `ContinuousPaper = True` or `Custom` Paper size, the printed document may be cut as this PDF printer supports a limited number of paper kinds and doesn't support custom paper size. Hence, it tries to print on its default paper size, which leads to the cut page content. -If you test printing the same report with [Foxit PDF](https://www.foxit.com/pdf-reader/) Printer, the report would most probably be printed as expected to a PDF file as this PDF printer supports custom paper. +If you test printing the same report with [Foxit PDF](https://www.foxit.com/pdf-reader/) Printer, the report would most probably be printed as expected to a PDF file, as this PDF printer supports custom paper. -In such scenarios you may continue troubleshooting on the hardware side rather than your reports. As a first step, you may try printing a large single-page document outside Telerik Reporting with the same printer to confirm that the problem is not related to the Reporting functionality or settings. +In such scenarios, you may continue troubleshooting on the hardware side rather than your reports. As a first step, you may try printing a large single-page document outside Telerik Reporting with the same printer to confirm that the problem is not related to the Reporting functionality or settings. ## Solution Select, from the Printer Settings, a [`PaperKind`](/api/telerik.reporting.drawing.pagesettings#Telerik_Reporting_Drawing_PageSettings_PaperKind) with Paper Height that is sufficient to accommodate the printed single-page document. -For example, the physical label printer that we tested on is "Epson-TM-T20II-M267D". It supports few 'Roll Paper' paper kinds with a length of **3276mm**. When we select such a paper kind, usually, the long reports with `ContinuousPaper = True` are printed as expected. However, selecting a shorter paper when printing the same report may cut it when report's height is more than the printer paper size. +For example, the physical label printer that we tested on is "Epson-TM-T20II-M267D". It supports a few 'Roll Paper' paper kinds with a length of **3276mm**. When we select such a paper kind, usually, the long reports with `ContinuousPaper = True` are printed as expected. However, selecting a shorter paper when printing the same report may cut it when the report's height is more than the printer paper size. -If the printer doesn't support long paper, you need to set report's `ContinuousPaper` to `False` and print the document paginated, with [`PaperKind`](/api/telerik.reporting.drawing.pagesettings#Telerik_Reporting_Drawing_PageSettings_PaperKind) and [`PaperSize`](/api/telerik.reporting.drawing.pagesettings#Telerik_Reporting_Drawing_PageSettings_PaperSize) that are supported by the specific printer. +If the printer doesn't support long paper, you need to set the report's `ContinuousPaper` to `False` and print the document paginated, with [`PaperKind`](/api/telerik.reporting.drawing.pagesettings#Telerik_Reporting_Drawing_PageSettings_PaperKind) and [`PaperSize`](/api/telerik.reporting.drawing.pagesettings#Telerik_Reporting_Drawing_PageSettings_PaperSize) that are supported by the specific printer. diff --git a/knowledge-base/the-type-initializer-for-lock-threw-an-exception.md b/knowledge-base/the-type-initializer-for-lock-threw-an-exception.md index 8d0359383..bb4d20c3a 100644 --- a/knowledge-base/the-type-initializer-for-lock-threw-an-exception.md +++ b/knowledge-base/the-type-initializer-for-lock-threw-an-exception.md @@ -1,16 +1,16 @@ --- -title: The type initializer for Lock threw an exception error in HTML5 viewer in ASP.NET Core application -description: The type initializer for Lock threw an exception error in HTML5 viewer in ASP.NET Core application +title: The type initializer for Lock threw an exception error in the HTML5 viewer in an ASP.NET Core application +description: "Learn why the type initializer for Lock may throw an exception error in the HTML5 viewer in the ASP.NET Core application." type: troubleshooting -page_title: The type initializer for Lock threw an exception error in HTML5 viewer in ASP.NET Core application +page_title: The type initializer for Lock threw an exception error in the HTML5 viewer in the ASP.NET Core application slug: the-type-initializer-for-lock-threw-an-exception -position: tags: lock,html5,viewer,core ticketid: 1149503 res_type: kb --- ## Environment +
Product Version
@@ -18,28 +18,28 @@ res_type: kb - +
Product
Project Type.NET Core.NET
## Important note -The following article is applicable to Telerik Reporting versions prior to R1 2019. It elaborates on how to host Telerik Reporting REST Service and add HTML5 Report Viewer in an ASP.NET Core 2 web application. +The following article applies to Telerik Reporting versions before R1 2019. It elaborates on how to host the Telerik Reporting REST Service and add an HTML5 Report Viewer in an ASP.NET Core web application. -As of [Telerik Reporting R1 2019](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-r1-2019-13-0-19-116) we support report rendering runtime targeting .NET Core 2.1+ applications. For more information how to use reports in a .NET Core application for Windows and Linux platforms, please refer to [.NET Core Support]({%slug telerikreporting/using-reports-in-applications/dot-net-core-support%}) help article. +As of [Telerik Reporting R1 2019](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-r1-2019-13-0-19-116), we support report rendering runtime targeting .NET Core 2.1+ applications. For more information on how to use reports in a .NET Core application for Windows and Linux platforms, please refer to [.NET Core Support]({%slug telerikreporting/using-reports-in-applications/dot-net-core-support%}) help article. ## Description -When using HTML5 report viewer to display reports in .NET Core application an error is displayed in the viewer: "Error registering the viewer with the service. An error has occurred. The type initializer for 'Lock' threw an exception." +When using the HTML5 report viewer to display reports in a .NET Core application, an error is displayed in the viewer: "Error registering the viewer with the service. An error has occurred. The type initializer for 'Lock' threw an exception." ## Solution -Such errors occur when Telerik Reporting NuGet packages we provide for .NET Core projects are not compatible with the project. The packages are built against the full .NET Framework because the Reporting engine relies on the GDI+ API. Therefore, the packages will not work in the project that targets .NET Core framework as GDI+ is missing there. +Such errors occur when the Telerik Reporting NuGet packages we provide for .NET Core projects are not compatible with the project. The packages are built against the full .NET Framework because the Reporting engine relies on the GDI+ API. Therefore, the packages will not work in the project that targets .NET Core framework as GDI+ is missing there. If you wish to use the packages in .NET Core project use the following steps for creating the project: 1. In the New Project dialog, expand Installed > Visual C# > .NET Core, and select ASP.NET Core Web Application project template. Choose a name for the project and click OK. -2. On the New ASP.NET Core Web Application dialog select from the drop downs **.NET Framework** and ASP.NET Core 2. Next from the list of templates select Web API. +1. On the New ASP.NET Core Web Application dialog select from the drop downs **.NET Framework** and ASP.NET Core 2. Next from the list of templates select Web API. It is important to select .NET Framework from the drop down on the second step as this will set full .NET framework as the target framework of the project. @@ -50,4 +50,5 @@ When the service and the viewer are hosted in different domains it will be requi ## See Also * [HTML5 Report Viewer in ASP.NET Core 2]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/how-to-use-html5-report-viewer-in-an-asp.net-core-2.1-and-2.2-application%}) -* [How To: Add Telerik Reporting REST Web API to Web Application](telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/asp.net-web-api-implementation/how-to-add-telerik-reporting-rest-web-api-to-web-application) +* [Hosting the Telerik Reporting REST Service in an ASP.NET Application]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/asp.net-web-api-implementation/how-to-add-telerik-reporting-rest-web-api-to-web-application%}) +* [Hosting the Telerik Reporting REST Service in an ASP.NET Core Application in .NET Core 2.1 and 2.2]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/asp.net-core-web-api-implementation/how-to-host-reports-service-in-asp.net-core-2.1-and-2.2%}) diff --git a/knowledge-base/wrap-text-data-labels-telerik-reporting.md b/knowledge-base/wrap-text-data-labels-telerik-reporting.md index a372de3df..64c82b83f 100644 --- a/knowledge-base/wrap-text-data-labels-telerik-reporting.md +++ b/knowledge-base/wrap-text-data-labels-telerik-reporting.md @@ -38,7 +38,7 @@ To wrap text in data labels for a Column chart in the Graph Report Item, use the This function replaces spaces with a new line character, effectively wrapping the text. -Additionally, consider extending expressions for more complex formatting needs. For more details, refer to the [Extending Expressions](%slug telerikreporting/designing-reports/connecting-to-data/expressions/extending-expressions/overview%) section in the documentation. +Additionally, consider extending expressions for more complex formatting needs. For more details, refer to the [Extending Expressions]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/extending-expressions/overview%}) section in the documentation. An alternative approach is to **rotate** the labels and center the text to fit the data labels within the column's width. @@ -58,4 +58,4 @@ An alternative approach is to **rotate** the labels and center the text to fit t * [Graph Report Item]({%slug telerikreporting/designing-reports/report-structure/graph/overview%}) * [Column Chart Type]({%slug telerikreporting/designing-reports/report-structure/graph/chart-types/column-charts/overview%}) * [Text Functions in Expressions]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/expressions-reference/functions/text-functions%}) -* [Extending Expressions Overview](%slug telerikreporting/designing-reports/connecting-to-data/expressions/extending-expressions/overview%) +* [Extending Expressions Overview]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/extending-expressions/overview%}) diff --git a/licensing/add-license-key-ci-services.md b/licensing/add-license-key-ci-services.md index 28b3d3485..6515bc56c 100644 --- a/licensing/add-license-key-ci-services.md +++ b/licensing/add-license-key-ci-services.md @@ -1,6 +1,7 @@ --- title: Add License Key to CI Services page_title: "Learn how to add your License Key to CI/CD Services." +description: "Learn how to add the required Telerik Reporting License Key to CI/CD Services after the 2025 Q1 (19.0.25.211) release." slug: license-key-ci-services tags: license, key, telerik, reporting, ci, cd published: True diff --git a/licensing/license-errors-and-warnings.md b/licensing/license-errors-and-warnings.md index ee0b68831..b975a971d 100644 --- a/licensing/license-errors-and-warnings.md +++ b/licensing/license-errors-and-warnings.md @@ -1,6 +1,7 @@ --- title: Errors and Warnings page_title: "Learn about Errors and Warnings in Telerik Reporting Licensing." +description: "Learn about Errors and Warnings in Telerik Reporting Licensing after the 2025 Q1 (19.0.25.211) release." slug: license-errors-and-warnings tags: license, telerik, reporting, questions, errors, warnings published: True diff --git a/licensing/license-faq.md b/licensing/license-faq.md index eaad032ae..92c1dadd3 100644 --- a/licensing/license-faq.md +++ b/licensing/license-faq.md @@ -1,6 +1,7 @@ --- title: FAQs page_title: "Frequently Asked Questions about Telerik Reporting Licensing." +description: "Learn the answers to the most Frequently Asked Questions about the Telerik Reporting License Key required after the 2025 Q1 (19.0.25.211) release." slug: license-frequently-asked-questions tags: license, telerik, reporting, faq, questions published: True diff --git a/licensing/setting-up-your-telerik-reporting-license-key.md b/licensing/setting-up-your-telerik-reporting-license-key.md index 1876488ba..4217dfe0d 100644 --- a/licensing/setting-up-your-telerik-reporting-license-key.md +++ b/licensing/setting-up-your-telerik-reporting-license-key.md @@ -1,6 +1,7 @@ --- title: Setting Up Telerik Reporting License Key page_title: "Learn how to set up the Telerik Reporting License Key." +description: "Learn how to set up the required Telerik Reporting License Key after the 2025 Q1 (19.0.25.211) release." slug: license-key tags: license, key, telerik, reporting, licensing published: True diff --git a/upgrade/2025/2025-q2-19-1-25-521.md b/upgrade/2025/2025-q2-19-1-25-521.md index 7bd94ba85..70efe522b 100644 --- a/upgrade/2025/2025-q2-19-1-25-521.md +++ b/upgrade/2025/2025-q2-19-1-25-521.md @@ -15,10 +15,10 @@ This article explains the manual changes required when upgrading to Telerik Repo ## Changes ### Unified distribution for trial and commercial packages -Streamlined user experience by consolidating trial and commercial packages into a single unified distribution for Telerik UI libraries. Access is now managed through a license key file, eliminating the need for separate trial downloads. For more information, please refer to the [documentation article](%slug license-key%). +Streamlined user experience by consolidating trial and commercial packages into a single unified distribution for Telerik UI libraries. Access is now managed through a license key file, eliminating the need for separate trial downloads. For more information, please refer to the [documentation article]({%slug license-key%}). ### HTML5 Report Viewer -The viewer now uses Sass theming mechanism based on [Kendo UI themes v10.2.0](https://www.telerik.com/design-system/docs/themes/get-started/introduction/) and [Kendo UI for jQuery 2025.1.227](https://www.telerik.com/support/whats-new/kendo-ui/release-history/kendo-ui-for-jquery-2025-1-227). Refer to [this article]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/manual-setup%}) for guidance on mitigating potential issues. +The viewer now uses the Sass theming mechanism based on [Kendo UI themes v10.2.0](https://www.telerik.com/design-system/docs/themes/get-started/introduction/) and [Kendo UI for jQuery 2025.1.227](https://www.telerik.com/support/whats-new/kendo-ui/release-history/kendo-ui-for-jquery-2025-1-227). Refer to [this article]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/manual-setup%}) for guidance on mitigating potential issues. ### WinUI Report Viewer @@ -26,7 +26,7 @@ The viewer is built with Telerik UI for WinUI __4.0.0__. WinUI Report Viewer tar ### WPF Report Viewer for .NET Framework -The viewer is built with Telerik UI Controls for WPF __2025.2.521.462__. If you are using a newer version, consider adding binding redirects. For more information see: [How to Add report viewer to a WPF .NET Framework project]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/wpf-application/how-to-add-report-viewer-to-a-wpf-.net-framework-project%}). +The viewer is built with Telerik UI Controls for WPF __2025.2.521.462__. If you are using a newer version, consider adding binding redirects. For more information, see: [How to Add report viewer to a WPF .NET Framework project]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/wpf-application/how-to-add-report-viewer-to-a-wpf-.net-framework-project%}). ### WPF Report Viewer for .NET 6