Skip to content

docs: update undefined not iterable article #1713

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

petar-i-todorov
Copy link
Contributor

No description provided.

Copilot

This comment was marked as outdated.

@petar-i-todorov petar-i-todorov requested a review from Copilot June 13, 2025 21:06
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates a documentation article to reflect changes in behavior when using HTML5-based report viewers, specifically addressing a TypeError issue.

  • Updated title and description for clarity regarding HTML5-based report viewers.
  • Revised the cause section to reference a specific version (19.1.25.521) and updated the solution section to emphasize using the ready event.
Comments suppressed due to low confidence (2)

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

  • [nitpick] Consider rephrasing 'immediately after it' to 'immediately after the initialization call' for clarity in explaining the cause.
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()` immediately after it do not behave as expected.

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

  • [nitpick] Ensure consistent naming by aligning on 'HTML5-based report viewers' throughout the document if that is the preferred terminology.
Place logic that relies on the report viewer being fully initialized, such as the `reportViewer.reportSource()` calls, inside the `ready` event 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:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants