Update how-to-change-report-parameter-date-format-in-html5-mvc-report… (#783)
* Update how-to-change-report-parameter-date-format-in-html5-mvc-report-viewer.md * Update requirements-and-browser-support.md * Update angular-report-viewer-overview.md * Update options.md * Update overview.md * Update overview.md * Update how-to-add-report-viewer-to-a-silverlight-application.md * Update programmatic-initialization-of-report-parameter-values-in-telerik-reporting-silverlight-viewer.md * Update send-telerik-report-in-an-e-mail.md * Update picturebox.md * Update about-telerik-reporting.md * Update troubleshooting-design-time-reportviewer-control-reportsource-property-from-the-property-grid-does-not-show-available-reports.md * Update overview.md * Update uncaught-typeerror-getClientRects-is-not-a-function.md * Update overview.md * Update using-ms-access-database-in-the-report .md * Update csv-device-information-settings.md
This commit is contained in:
Todor Arabadzhiev
GitHub
Родитель
f5266e9e0e
Коммит
5e034e67bd
|
|
@ -6,7 +6,7 @@ slug: telerikreporting/designing-reports/overview
|
|||
tags: telerik, reporting, creating, designing, reports, overview
|
||||
published: True
|
||||
position: 0
|
||||
previous_url: /designing-reports
|
||||
previous_url: /designing-reports, /creating-the-report
|
||||
---
|
||||
|
||||
# Creating Reports Overview
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ slug: telerikreporting/using-reports-in-applications/export-and-configure/config
|
|||
tags: csv,device,information,settings
|
||||
published: True
|
||||
position: 6
|
||||
previous_url: /device-information-settings-csv
|
||||
previous_url: /device-information-settings-csv, /using-reports-in-applications/export-and-configure/configure-the-export-formats/csv-device-information-settings
|
||||
---
|
||||
<style>
|
||||
table th:first-of-type {
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ slug: telerikreporting/using-reports-in-applications/display-reports-in-applicat
|
|||
tags: how,to,add,report,viewer,to,a,silverlight,application
|
||||
published: True
|
||||
position: 1
|
||||
previous_url: /silverlight-report-viewer-embedding_the_Silverlight_Viewer
|
||||
previous_url: /silverlight-report-viewer-embedding_the_Silverlight_Viewer, /silverlight-report-viewer-embedding-the-silverlight-viewer
|
||||
---
|
||||
|
||||
# How to Add report viewer to a Silverlight application
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ slug: telerikreporting/using-reports-in-applications/display-reports-in-applicat
|
|||
tags: angular,report,viewer,overview
|
||||
published: True
|
||||
position: 0
|
||||
previous_url: /angular-report-viewer
|
||||
previous_url: /angular-report-viewer, /using-reports-in-applications/display-reports-in-applications/web-application/angular-report-viewer/angular-report-viewer-overview
|
||||
---
|
||||
|
||||
# Angular Report Viewer Overview
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ slug: telerikreporting/using-reports-in-applications/display-reports-in-applicat
|
|||
tags: options
|
||||
published: True
|
||||
position: 0
|
||||
previous_url: /angular-report-viewer-api-options
|
||||
previous_url: /angular-report-viewer-api-options, /using-reports-in-applications/display-reports-in-applications/web-application/angular-report-viewer/angular-report-viewer-api-options
|
||||
---
|
||||
<style>
|
||||
table th:first-of-type {
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ slug: telerikreporting/using-reports-in-applications/display-reports-in-applicat
|
|||
tags: overview
|
||||
published: True
|
||||
position: 0
|
||||
previous_url: /webforms-report-viewer-controls-overview
|
||||
previous_url: /webforms-report-viewer-controls-overview, /webforms-report-viewer-controls-system-requirements
|
||||
---
|
||||
|
||||
# HTML5 ASP.NET Web Forms Report Viewer Overview
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ slug: telerikreporting/using-reports-in-applications/display-reports-in-applicat
|
|||
tags: overview
|
||||
published: True
|
||||
position: 0
|
||||
previous_url: /html5-report-viewer
|
||||
previous_url: /html5-report-viewer, /using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/overview
|
||||
---
|
||||
|
||||
# HTML5 Report Viewer Overview
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ slug: telerikreporting/using-reports-in-applications/display-reports-in-applicat
|
|||
tags: requirements,and,browser,support
|
||||
published: True
|
||||
position: 1
|
||||
previous_url: /html5-report-viewer-system-requirements, /using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/requirements-and-browser-support
|
||||
previous_url: /html5-report-viewer-system-requirements, /using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/requirements-and-browser-support, /html5-report-viewer-widget-requirements
|
||||
---
|
||||
|
||||
# Requirements and Browser Support
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ description: "Learn more about the concepts and logic behind Telerik Reporting."
|
|||
slug: on-telerik-reporting
|
||||
tags: telerik, reporting, basic, concepts, explanations, logic
|
||||
published: True
|
||||
previous_url: /best-practices-solution-structure
|
||||
position: 0
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ With this approach the new date format is assigned to the **kendoDatePicker** th
|
|||
|
||||
The following script section should be added (in the head section) to the **ReportViewer.cshtml** file
|
||||
|
||||
```html
|
||||
````HTML
|
||||
<script>
|
||||
var dateUpdated = false;// Flag to indicate that date format has been set
|
||||
|
||||
|
|
@ -59,11 +59,11 @@ The following script section should be added (in the head section) to the **Repo
|
|||
}
|
||||
}
|
||||
</script>
|
||||
```
|
||||
````
|
||||
|
||||
The following script shows how the ReportViewer description would look like in the **.cshtml** file after adding the UpdateUi event.
|
||||
|
||||
```cs
|
||||
````CSharp
|
||||
<body>
|
||||
@(Html.TelerikReporting().ReportViewer()
|
||||
.Id("reportViewer1")
|
||||
|
|
@ -80,14 +80,13 @@ The following script shows how the ReportViewer description would look like in t
|
|||
)
|
||||
)
|
||||
</body>
|
||||
```
|
||||
````
|
||||
|
||||
## Solution 2 - Create a custom parameter editor for the DateTime Parameter.
|
||||
|
||||
The following script section should be added (in the head section) to the **ReportViewer.cshtml** file
|
||||
|
||||
|
||||
```html
|
||||
````HTML
|
||||
<script>
|
||||
function customMatch(parameter) {
|
||||
return parameter.type === "System.DateTime";
|
||||
|
|
@ -129,12 +128,11 @@ The following script section should be added (in the head section) to the **Repo
|
|||
};
|
||||
}
|
||||
</script>
|
||||
```
|
||||
|
||||
````
|
||||
|
||||
The property *ParameterEditors* of the ReportViewer should be set in the body section of the **ReportViewer.cshtml file**, and it will look like this
|
||||
|
||||
```cs
|
||||
````CSharp
|
||||
<body>
|
||||
@(Html.TelerikReporting().ReportViewer()
|
||||
.Id("reportViewer1")
|
||||
|
|
@ -155,12 +153,12 @@ The property *ParameterEditors* of the ReportViewer should be set in the body se
|
|||
)
|
||||
)
|
||||
</body>
|
||||
```
|
||||
````
|
||||
|
||||
## Notes
|
||||
|
||||
In Telerik Reporting ,the default element for editing DateTime Parameters is **kendoDatePicker**. Its default DateTime format depends on the [culture](../designing-reports-report-globalization) settings of the environment.
|
||||
In Telerik Reporting ,the default element for editing DateTime Parameters is **kendoDatePicker**. Its default DateTime format depends on the [culture]({%slug telerikreporting/designing-reports/report-globalization%}) settings of the environment.
|
||||
|
||||
## See Also
|
||||
|
||||
[How to Create a Custom Parameter Editor](../html5-report-viewer-howto-custom-parameter-editor).
|
||||
* [How to Create a Custom Parameter Editor](../html5-report-viewer-howto-custom-parameter-editor).
|
||||
|
|
|
|||
|
|
@ -27,21 +27,21 @@ res_type: kb
|
|||
|
||||
Usually, one may control the report appearance and the data it displays through report parameters. The Silverlight report viewer, offers built-in user interface that enables end users to interact with the reports. Still, there are cases when one may further need to control the report definition according to a custom logic that runs in the client application. However, since we have introduced the [Silverlight Report Viewer](../silverlight-report-viewer-embedding-the-silverlight-viewer), the greatest challenge our clients have faced is that there is no direct access to the report definition in the Silverlight application.
|
||||
|
||||
|
||||
## Solution
|
||||
|
||||
To provide the ability to specify the parameter values, we have decided to add a new event to the **ReportViewer** control called **RenderBegin**. As its name suggests it is raised just before the actual request for rendering is sent and has two arguments: **sender** which is an instance of the **ReportViewer** control and an instance of the **RenderBeginEventArgs** class.
|
||||
|
||||
The parameter values can now be set through the **ParameterValues** property of the event argument. It is a **name** (string) – **value** (object) dictionary in which the key is the parameter name and the value is the designated parameter value.
|
||||
|
||||
Here is a simple example of setting report parameter values programmatically. Consider a scenario in which we want to set initial values for the cascading parameters of the [Product Line Sales](../product-line-sales) report:
|
||||
Here is a simple example of setting report parameter values programmatically. Consider a scenario in which we want to set initial values for the cascading parameters of the [Product Line Sales](https://demos.telerik.com/reporting/product-line-sales) report:
|
||||
|
||||
```cs
|
||||
````CSharp
|
||||
public MainPage()
|
||||
{
|
||||
InitializeComponent();
|
||||
this.ReportViewer1.RenderBegin += new RenderBeginEventHandler(ReportViewer1_RenderBegin);
|
||||
}
|
||||
|
||||
void ReportViewer1_RenderBegin(object sender, RenderBeginEventArgs args)
|
||||
{
|
||||
//single value parameter
|
||||
|
|
@ -49,13 +49,10 @@ args.ParameterValues["ProductCategory"] = "Components";
|
|||
//multi value parameter
|
||||
args.ParameterValues["ProductSubcategory"] = new object[] { "Brakes", "Chains" };
|
||||
}
|
||||
```
|
||||
````
|
||||
|
||||
## Notes
|
||||
|
||||
The Silverlight Report Viewer runs on the **client** and the reports are on the **server**, there is no way to know whether or not a parameter with a given name in the dictionary exists for the specified report on the server. The match is performed on the server **after** the request is sent. For this reason you have to pay extra attention that the names in the dictionary and the report parameter names in the report definition match completely. This is valid for their types as well.
|
||||
|
||||
> The values in the example are hardcoded for simplicity and in real project you can take the actual values from your **Silverlight UI** controls. Notice that passing multiple values is achieved through an object array. In all other cases the value is set directly with its actual type.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ slug: send-telerik-report-in-an-e-mail
|
|||
res_type: kb
|
||||
---
|
||||
|
||||
> Since [Progress® Telerik® Reporting R3 2018 (12.2.18.912)](../release-history/progress-telerik-reporting-r3-2018-12-2-18-912) release this feature is supported out of the box. For more information, see the [Send Mail Message](../html5-report-viewer-send-mail) help article.
|
||||
> Since [R3 2018 (12.2.18.912)](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-r3-2018-12-2-18-912) release this feature is supported out of the box. For more information, see the [Send Mail Message](../html5-report-viewer-send-mail) help article.
|
||||
|
||||
## Environment
|
||||
<table>
|
||||
|
|
@ -35,5 +35,4 @@ In case using HTML is a requirement, you can [export a report programmatically](
|
|||
|
||||
## See Also
|
||||
|
||||
[How to design a cross-client / browser compatible email](http://stackoverflow.com/questions/1531630/how-to-design-a-cross-client-browser-compatible-email)
|
||||
|
||||
* [How to design a cross-client / browser compatible email](http://stackoverflow.com/questions/1531630/how-to-design-a-cross-client-browser-compatible-email)
|
||||
|
|
|
|||
|
|
@ -20,15 +20,16 @@ res_type: kb
|
|||
|
||||
|
||||
## Description
|
||||
|
||||
I want to show my report in a ReportViewer control, but when I click on the arrow in the ReportSource property from the property grid, it does not show available reports - what is wrong?
|
||||
|
||||
## Solution
|
||||
Follow our [best practices](../best-practices-solution-structure) and have the report in a separate class library that is referenced in the application or website. Check if the class library containing the report is referenced in your application/website and that you have rebuilt the application/website.
|
||||
|
||||
Follow our [best practices]({%slug on-telerik-reporting%}) and have the report in a separate class library that is referenced in the application or website. Check if the class library containing the report is referenced in your application/website and that you have rebuilt the application/website.
|
||||
|
||||
The most reliable way to specify a report for the ReportViewer is to do this programmatically. For example, if you're using the ASP.NET Web Forms Report Viewer, on the Page_Load event of the page:
|
||||
|
||||
#### _CSharp Example_
|
||||
```CSharp
|
||||
````CSharp
|
||||
protected void Page_Load(object sender, EventArgs e)
|
||||
{
|
||||
if (!IsPostBack)
|
||||
|
|
@ -38,9 +39,8 @@ protected void Page_Load(object sender, EventArgs e)
|
|||
this.ReportViewer1.ReportSource = typeReportSource;
|
||||
}
|
||||
}
|
||||
```
|
||||
#### _VB Example_
|
||||
```VB
|
||||
````
|
||||
````VB
|
||||
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
|
||||
If Not IsPostBack Then
|
||||
Dim typeReportSource As New Telerik.Reporting.TypeReportSource()
|
||||
|
|
@ -49,4 +49,5 @@ Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Han
|
|||
ReportViewer1.RefreshReport()
|
||||
End If
|
||||
End Sub
|
||||
```
|
||||
````
|
||||
|
||||
|
|
|
|||
|
|
@ -20,28 +20,32 @@ res_type: kb
|
|||
|
||||
|
||||
## Description
|
||||
|
||||
When attempting to open the export options from the report viewer's toolbar, the an error occurs in browser console preventing the export process.
|
||||
|
||||
## Error Message
|
||||
```
|
||||
|
||||
````
|
||||
Uncaught TypeError: X.getClientRects is not a function
|
||||
|
||||
at M.fn.init.offset (jquery-3.3.1.js:10020)
|
||||
at init._position (telerikReportViewer.kendo-<VERSION>.min.js:3)
|
||||
at init.open (telerikReportViewer.kendo-<VERSION>.min.js:3)
|
||||
at telerikReportViewer.kendo-<VERSION>.min.js:3
|
||||
```
|
||||
````
|
||||
|
||||
## Cause\Possible Cause(s)
|
||||
|
||||
In general, the **getClientRects** method is used by jQuery. We do not use this method in the viewer code.
|
||||
|
||||
Telerik Report Viewer uses Kendo UI for jQuery widget for the export menu. The version of Kendo UI for jQuery served by default from the Telerik Reporting REST service is not compatible with jQuery 3 or above (the getClientRects error is observed). In R2 2018, UI for ASP.NET AJAX has upgraded their built-in [jQuery version](https://docs.telerik.com/devtools/aspnet-ajax/general-information/using-jquery/using-jquery#jquery-version-history-in-telerik-ui-controls) from 1.11.1 to 3.3.1.
|
||||
|
||||
|
||||
## Solution
|
||||
|
||||
There are two possible ways to fix the error:
|
||||
1. Use the previous jQuery version used by the UI for ASP.NET AJAX components. This can be done by following the [Using External jQuery](https://docs.telerik.com/devtools/aspnet-ajax/general-information/using-jquery/using-jquery#including-external-jquery) help article.
|
||||
2. Reference the latest Kendo UI for jQuery in your application. So, this version will be used instead of the older version provided by the Telerik Reporting REST service. According to the [Kendo UI documentation](https://docs.telerik.com/kendo-ui/intro/installation/prerequisites#supported-jquery-versions), the latest version supports jQuery 3.3.1 and this fixes the error message.
|
||||
|
||||
## Notes
|
||||
Another possible reason to get this error message is if the jQuery script is loaded multiple times on the page. Please make sure that jQuery script is loaded only once, and that the application meets the [viewer requirements](../webforms-report-viewer-controls-system-requirements).
|
||||
|
||||
Another possible reason to get this error message is if the jQuery script is loaded multiple times on the page. Please make sure that jQuery script is loaded only once, and that the application meets the [viewer requirements]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-asp.net-web-forms-report-viewer/overview%}#requirements).
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ res_type: kb
|
|||
<tbody>
|
||||
<tr>
|
||||
<td>Product Version</td>
|
||||
<td>13.1.19.618</td>
|
||||
<td>13.1.19.618 and above</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Product</td>
|
||||
|
|
@ -26,15 +26,20 @@ res_type: kb
|
|||
|
||||
|
||||
## Description
|
||||
|
||||
This article lists the required steps for setting MS Access Database and using it in the report.
|
||||
|
||||
## Solution
|
||||
|
||||
1. Create a sample database in **Access**:
|
||||
|
||||
2. [Create a new report](../creating-the-report) and insert **SQL Data Source**.
|
||||
|
||||
|
||||
|
||||
2. [Create a new report]({%slug telerikreporting/designing-reports/overview%}) and insert **SQL Data Source**.
|
||||
3. Click on **Build new data connection** and select **OleDB Data Provider** from the dropdown.
|
||||
4. The data source has to be a **Microsoft Access Database File (OLE DB)**.
|
||||
5. Browse to the file’s location.
|
||||
6. Click **OK** and finish the Wizard with the default settings.
|
||||
7. In the **Configure data source command dialog**, click on **Query Builder** and mark the desired fields:
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ slug: telerikreporting/designing-reports/report-structure/picturebox
|
|||
tags: telerik, reporting, report, items, picturebox, set, value, bind, binary, images, svg, base64, uri, string, literals, clip, render, position
|
||||
published: True
|
||||
position: 9
|
||||
previous_url: /report-items-picture-box
|
||||
previous_url: /report-items-picture-box, /designing-reports/report-structure/picturebox
|
||||
---
|
||||
<style>
|
||||
table th:first-of-type {
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ slug: telerikreporting/upgrade/overview
|
|||
tags: telerik, reporting, upgrading, major, minor, releases, desktop, website, other, projects, manually, overview
|
||||
published: True
|
||||
position: 0
|
||||
previous_url: /installation-upgrading-newer-version, /installation-upgrading-newer_version
|
||||
previous_url: /installation-upgrading-newer-version, /installation-upgrading-newer_version, /upgradepathoverview
|
||||
---
|
||||
|
||||
# Upgrading Telerik Reporting
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче