Skip to content

Commit 1641baf

Browse files
docs: add kb on addressing custom parameter editors issue in 19.1.25.521 (#1723)
* docs: add kb on addressing custom parameter editors issue in 19.1.25.521 * docs: remove reference * Update custom-parameter-editors-stopped-working-19-1-25-521.md --------- Co-authored-by: Todor Arabadzhiev <[email protected]>
1 parent 6fe721b commit 1641baf

File tree

1 file changed

+91
-0
lines changed

1 file changed

+91
-0
lines changed
Lines changed: 91 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,91 @@
1+
---
2+
title: Custom Parameter Editors Stopped Working in Progress Telerik Reporting Version 19.1.25.521
3+
description: Resolve the issue with custom parameter editors not displaying in Telerik HTML5 Report Viewer version 19.1.25.521.
4+
type: troubleshooting
5+
page_title: HTML5 Report Viewer Custom Parameter Editor Issue
6+
meta_title: HTML5 Report Viewer Custom Parameter Editor Issue
7+
slug: custom-parameter-editor-stopped-working
8+
tags: telerik reporting, html5 report viewer, custom parameter editor, parameter editors, javascript
9+
res_type: kb
10+
---
11+
12+
## Environment
13+
14+
<table>
15+
<tbody>
16+
<tr>
17+
<td>Product</td>
18+
<td>Progress® Telerik® Reporting</td>
19+
</tr>
20+
<tr>
21+
<td>Version</td>
22+
<td>19.1.25.521</td>
23+
</tr>
24+
</tbody>
25+
</table>
26+
27+
## Description
28+
29+
After upgrading to version 19.1.25.521, parameter editors implemented for the HTML5 Report Viewer no longer appear as intended. The underlying code is not executed, causing the parameter editors to revert to the default implementation.
30+
31+
## Cause
32+
33+
The issue is caused by changes introduced in version 19.1.25.521 of Telerik Reporting. These changes were made to ensure compatibility with [Kendo UI Sass themes](https://www.telerik.com/kendo-jquery-ui/documentation/styles-and-layout/sass-themes/overview), but they inadvertently affected the rendering of custom parameter editors.
34+
35+
## Solution
36+
37+
To resolve this issue, modify the `telerikReportViewer-19.1.25.521.js` file to include your custom parameter editor implementation. Follow these steps:
38+
39+
1. **Locate and copy the JavaScript file**
40+
41+
Find the `telerikReportViewer-19.1.25.521.js` file in the installation directory:
42+
43+
`C:\Program Files (x86)\Progress\Telerik Reporting R3 2025\Html5\ReportViewer\js\telerikReportViewer-19.1.25.521.js`
44+
45+
Copy this file to your project's directory.
46+
47+
1. **Find the ParameterEditors array**
48+
49+
Open the copied file and search for the `ParameterEditors` array definition.
50+
51+
1. **Customize the editor logic**
52+
53+
Choose one of the following approaches based on your requirements:
54+
55+
**Option A: Override an existing editor type**
56+
57+
If you want to override the editor for a specific type (e.g., DateTime), locate the existing entry (for example, the entry with `match: parameterEditorsMatch.DateTime`) and replace the `createEditor` function with your own implementation:
58+
59+
````javascript
60+
var ParameterEditors = [
61+
// ...existing editors...
62+
{
63+
match: parameterEditorsMatch.DateTime,
64+
createEditor: createCustomEditor
65+
},
66+
// ...remaining editors...
67+
];
68+
````
69+
70+
**Option B: Add a new custom editor**
71+
72+
If you want to use your own matching logic, add a new entry to the end of the `ParameterEditors` array:
73+
74+
````javascript
75+
var ParameterEditors = [
76+
// ...existing editors...
77+
{
78+
match: customMatch,
79+
createEditor: createCustomEditor
80+
}
81+
];
82+
````
83+
84+
85+
1. **Update your project references**
86+
87+
Replace the reference to the original `telerikReportViewer-19.1.25.521.js`/`telerikReportViewer-19.1.25.521.min.js` file with the path to your modified version.
88+
89+
1. **Test the implementation**
90+
91+
Test the implementation to verify that the custom parameter editor renders correctly and functions as expected.

0 commit comments

Comments
 (0)