Skip to content

Commit aa2d841

Browse files
docs: update undefined not iterable article (#1713)
* docs: address dotnet 6 deprecation issues * docs: update undefined not iterable article * revert changes * revert * Update knowledge-base/telerik-reportviewer-typeerror-undefined-is-not-iterable.md Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com> * docs: make it more technically accurate --------- Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com>
1 parent 95d2558 commit aa2d841

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

knowledge-base/telerik-reportviewer-typeerror-undefined-is-not-iterable.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: TypeError undefined is not iterable in Telerik ReportViewer
3-
description: Resolving the 'TypeError undefined is not iterable' error when previewing a report with Telerik ReportViewer.
2+
title: TypeError undefined is not iterable in HTML5-based report viewers
3+
description: Learn how to resolve the 'TypeError undefined is not iterable' error when previewing a report in HTML5-based report viewers.
44
type: troubleshooting
55
page_title: Fix TypeError undefined is not iterable in HTML5-based report viewer
66
slug: telerik-reportviewer-typeerror-undefined-is-not-iterable
@@ -33,11 +33,11 @@ When attempting to preview a report using an HTML5-based report viewer, the foll
3333

3434
## Cause
3535

36-
This issue occurs due to a breaking change in the latest version, where the report viewer is no longer fully initialized immediately after the `$("#reportViewer1").telerik_ReportViewer` call. As a result, subsequent calls like `reportViewer.reportSource()` immediately after initialization do not behave as expected.
36+
This issue occurs due to a breaking change in the 19.1.25.521 version, where the report viewer is no longer fully initialized immediately after the `$("#reportViewer1").telerik_ReportViewer` call. As a result, subsequent calls like `reportViewer.reportSource()` will fail because the viewer instance is not yet ready.
3737

3838
## Solution
3939

40-
Use the `ready` event to ensure the report viewer is fully initialized before setting the report source. For example, in the HTML5 report viewer, this would look as follows:
40+
Place logic that relies on the report viewer being fully initialized, such as the `reportViewer.reportSource()` calls, inside the `ready` event handler instead. For example, in the [HTML5 report viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/overview%}), this would look as follows:
4141

4242
````javascript
4343
$("#reportViewer1")

0 commit comments

Comments
 (0)